From: Christoph Hellwig <hch@infradead.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Nikanth Karthikesan <knikanth@suse.de>,
Jens Axboe <jens.axboe@oracle.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Kernel 2.6.30.4 loop(..?) regression (& with/2.6.31-rc6)
Date: Wed, 26 Aug 2009 17:27:32 -0400 [thread overview]
Message-ID: <20090826212732.GA18124@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.00.0908261717001.1594@p34.internal.lan>
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.
next prev parent reply other threads:[~2009-08-26 21:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 8:39 Kernel 2.6.30.4 XFS(..?) regression Justin Piszcz
2009-08-08 19:31 ` Felix Blyakher
2009-08-09 10:09 ` Justin Piszcz
2009-08-11 10:58 ` Kernel 2.6.30.4 XFS(..?) regression (happened again) Justin Piszcz
2009-08-16 2:23 ` Christoph Hellwig
2009-08-17 14:25 ` Justin Piszcz
2009-08-22 10:27 ` Kernel 2.6.30.4 XFS(..?) regression (& with/2.6.31-rc6) Justin Piszcz
2009-08-22 14:25 ` Christoph Hellwig
2009-08-22 14:45 ` Justin Piszcz
2009-08-22 20:15 ` Christoph Hellwig
2009-08-22 20:46 ` Justin Piszcz
2009-08-22 20:55 ` Christoph Hellwig
2009-08-22 21:01 ` Justin Piszcz
2009-08-23 22:45 ` Christoph Hellwig
2009-08-24 11:04 ` Justin Piszcz
2009-08-26 13:50 ` Justin Piszcz
2009-08-26 18:02 ` Kernel 2.6.30.4 loop(..?) " Christoph Hellwig
2009-08-26 21:19 ` Justin Piszcz
2009-08-26 21:27 ` Christoph Hellwig [this message]
2009-08-26 21:31 ` Justin Piszcz
2009-08-28 11:23 ` Justin Piszcz
2009-08-28 16:55 ` Christoph Hellwig
2009-09-02 11:45 ` Justin Piszcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090826212732.GA18124@infradead.org \
--to=hch@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=jpiszcz@lucidpixels.com \
--cc=knikanth@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox