Date: Fri, 12 Mar 2004 18:34:23 -0800
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
Message-Id: <20040312183423.71d7bbb9.akpm@osdl.org>
In-Reply-To: <20040313004707.GA389@schmorp.de>
References: <20040313004707.GA389@schmorp.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1061
Lines: 25

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?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/