[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1291946360-sup-154@think>
Date: Thu, 09 Dec 2010 21:00:07 -0500
From: Chris Mason <chris.mason@...cle.com>
To: Mike Fedyk <mfedyk@...efedyk.com>
Cc: Andi Kleen <andi@...stfloor.org>, Jon Nelson <jnelson@...poni.net>,
"Ted Ts'o" <tytso@....edu>, Mike Snitzer <snitzer@...hat.com>,
Matt <jackdachef@...il.com>, Milan Broz <mbroz@...hat.com>,
linux-btrfs <linux-btrfs@...r.kernel.org>,
dm-devel <dm-devel@...hat.com>,
Linux Kernel <linux-kernel@...r.kernel.org>,
htd <htd@...cy-poultry.org>, htejun <htejun@...il.com>,
linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: hunt for 2.6.37 dm-crypt+ext4 corruption? (was: Re: dm-crypt barrier support is effective)
Excerpts from Mike Fedyk's message of 2010-12-09 20:58:40 -0500:
> On Thu, Dec 9, 2010 at 5:38 PM, Chris Mason <chris.mason@...cle.com> wrote:
> > Excerpts from Andi Kleen's message of 2010-12-09 18:16:16 -0500:
> >> > 512MB.
> >> >
> >> > 'free' reports 75MB, 419MB free.
> >> >
> >> > I originally noticed the problem on really real hardware (thinkpad
> >> > T61p), however.
> >>
> >> If you can easily reproduce it could you try a git bisect?
> >
> > Do we have a known good kernel? I looked back through the thread and
> > didn't see any reports where the postgres test on ext4 passed in this
> > config.
> >
>
> 2.6.34.something. -- Any chance a newer kernel can be tested to be found good?
But he is triggering the ext4 corruption without dm-crypt. I think
dm-crypt was still used somewhere on the system during the test, just
not on the partitions that actually hit the corruption.
-chris
--
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