From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753821AbZHZVTL (ORCPT ); Wed, 26 Aug 2009 17:19:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753310AbZHZVTK (ORCPT ); Wed, 26 Aug 2009 17:19:10 -0400 Received: from lucidpixels.com ([75.144.35.66]:57365 "EHLO lucidpixels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751403AbZHZVTK (ORCPT ); Wed, 26 Aug 2009 17:19:10 -0400 Date: Wed, 26 Aug 2009 17:19:11 -0400 (EDT) From: Justin Piszcz To: Christoph Hellwig cc: Nikanth Karthikesan , Jens Axboe , linux-kernel@vger.kernel.org, xfs@oss.sgi.com Subject: Re: Kernel 2.6.30.4 loop(..?) regression (& with/2.6.31-rc6) In-Reply-To: <20090826180234.GC14019@infradead.org> Message-ID: References: <20090822142550.GA10003@infradead.org> <20090822201558.GA17955@infradead.org> <20090822205502.GA18904@infradead.org> <20090823224504.GA19942@infradead.org> <20090826180234.GC14019@infradead.org> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 26 Aug 2009, Christoph Hellwig wrote: > On Wed, Aug 26, 2009 at 09:50:27AM -0400, Justin Piszcz wrote: >> So far the uptime is 2 days, if it does not recur in the next 24-48 >> hours, do you recommend I follow up with the linux-crypto folks about >> this? It appears this could be the cause (no issues, as of yet). > > At this point it doesn't look crypto related anymore, but like some > bad interaction between layers once we add those fsync in the loop code. > > What filesystem does you loop image reside on? Anything else special? For the root filesystem, on / type xfs (rw,noatime) For larger partitions (per the cryptoloop doc) the partition itself is setup via cryptoloop and then XFS ontop of that. Nothing special. > Any way to trgiger it with just loop but not crypto, etc. Unfortunately not that I am aware of.. Would trying the kernel with the patch removed and mounted with -o nobarrier help to show us anything, or? > > _______________________________________________ > xfs mailing list > xfs@oss.sgi.com > http://oss.sgi.com/mailman/listinfo/xfs >