From: Andrew Morton <akpm@osdl.org>
To: Marc Lehmann <pcg@schmorp.de>
Cc: linux-kernel@vger.kernel.org, Joe Thornber <thornber@redhat.com>,
Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: strange ext3 corruption problem on 2.6.x
Date: Fri, 12 Mar 2004 18:34:23 -0800 [thread overview]
Message-ID: <20040312183423.71d7bbb9.akpm@osdl.org> (raw)
In-Reply-To: <20040313004707.GA389@schmorp.de>
Marc Lehmann <pcg@schmorp.de> wrote:
>
> I use lvm-over-raid5 and get these messages once a day (requiring a reboot
> afterwards):
>
> EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #4804801: directory entry across blocks - offset=0, inode=0, rec_len=50000,
> name_len=152
> Aborting journal on device dm-0.
(and fsck comes up clean)
There have been earlier reports of this. Too many for it to be some random
glitch. We've had similar reports in 2.4, usually with raid5.
I'm fairly confident in ext3 - it's hard to think of an ext3-level bug
which wouldn't have 10x as many reports from non-md users. But perhaps
some timing unique to the MD layer is triggering some ext3 bug.
Joe, Neil: have you spotted reports like this? Any suggestions as to how
to track it down a bit?
next prev parent reply other threads:[~2004-03-13 2:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-13 0:47 strange ext3 corruption problem on 2.6.x Marc Lehmann
2004-03-13 2:34 ` Andrew Morton [this message]
2004-03-13 2:40 ` Marc Singer
[not found] <20040314222929.GA23106@mark>
2004-03-15 3:41 ` Marc Lehmann
2004-03-18 7:25 ` Pavel Machek
[not found] <1zRh6-2V6-9@gated-at.bofh.it>
[not found] ` <1zRh6-2V6-7@gated-at.bofh.it>
2004-03-15 23:25 ` Thorild Selen
-- strict thread matches above, loose matches on Subject: below --
2004-03-23 7:33 John Pearson
2004-03-23 7:54 ` Andrew D Kirch
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=20040312183423.71d7bbb9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=pcg@schmorp.de \
--cc=thornber@redhat.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