[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090826212732.GA18124@infradead.org>
Date: Wed, 26 Aug 2009 17:27:32 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Justin Piszcz <jpiszcz@...idpixels.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Nikanth Karthikesan <knikanth@...e.de>,
Jens Axboe <jens.axboe@...cle.com>,
linux-kernel@...r.kernel.org, xfs@....sgi.com
Subject: Re: Kernel 2.6.30.4 loop(..?) regression (& with/2.6.31-rc6)
On Wed, Aug 26, 2009 at 05:19:11PM -0400, Justin Piszcz wrote:
> 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.
Just to make sure we have all data here - you see the problem only
with loop devices backed by XFS, only with loop devices backed by
raw partitions or with both?
>> 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?
Actually, yes - seeing what happens if you run plain 2.6.30 or 2.6.31-rc
without the backout patch, but with -o nobarrier would be very
interesting.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists