From: Theodore Tso <tytso@mit.edu>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Solofo.Ramangalahy@bull.net,
Jindrich Makovicka <makovick@gmail.com>,
linux-ext4@vger.kernel.org
Subject: Re: data corruption with ext4 (from 2.6.27.4) exposed by rtorrent
Date: Wed, 5 Nov 2008 15:42:23 -0500 [thread overview]
Message-ID: <20081105204223.GC9266@mit.edu> (raw)
In-Reply-To: <18706.44.567787.592343@frecb006361.adech.frec.bull.fr>
On Wed, Nov 05, 2008 at 09:21:00PM +0100, Solofo.Ramangalahy@bull.net wrote:
> Solofo.Ramangalahy@bull.net writes:
> > > The next question is whether the problem is more easily triggerred
> > > when under memory pressure.
> >
> > I was currently testing other kernels, but, right, I will retest with more memory.
>
> with -m 2048 I do not observe the problem.
>
> I should add that with 2.6.28-rc3 + ext4 patch queue, I am observing
> what seems to be lockdep bug:
> [ 31.603020] BUG: key c9f315a8 not in .data!
Aneesh has some new patches in the ext4 patch queue that add new
lockdep annotations. I'm guessing there's a problem there. Aneesh,
can you look into this? Solofo, can you send the .config you used
in case it was unique to replicating the problem?
- Ted
next prev parent reply other threads:[~2008-11-05 20:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 12:42 data corruption with ext4 (from 2.6.27.4) exposed by rtorrent Roc Valles
2008-11-03 13:40 ` Theodore Tso
2008-11-03 13:47 ` Cryptooctoploid
2008-11-03 14:09 ` Roc Valles
2008-11-03 15:34 ` Cryptooctoploid
2008-11-03 15:51 ` Jindrich Makovicka
2008-11-05 19:44 ` Solofo.Ramangalahy
2008-11-05 19:57 ` Theodore Tso
2008-11-05 20:09 ` Solofo.Ramangalahy
2008-11-05 20:21 ` Solofo.Ramangalahy
2008-11-05 20:42 ` Theodore Tso [this message]
2008-11-05 20:52 ` Solofo.Ramangalahy
2008-11-06 10:15 ` Aneesh Kumar K.V
2008-11-06 10:36 ` Solofo.Ramangalahy
2008-11-06 13:47 ` Solofo.Ramangalahy
2008-11-06 13:59 ` Aneesh Kumar K.V
2008-11-05 13:34 ` Cryptooctoploid
2008-11-05 16:16 ` Eric Sandeen
2008-11-05 17:25 ` Theodore Tso
2008-11-05 20:13 ` Cryptooctoploid
2008-11-06 9:00 ` Roc Valles
2008-11-06 9:31 ` Cryptooctoploid
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=20081105204223.GC9266@mit.edu \
--to=tytso@mit.edu \
--cc=Solofo.Ramangalahy@bull.net \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=makovick@gmail.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;
as well as URLs for NNTP newsgroup(s).