[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: ext3 badness in 2.6.0-test2



Andrew Morton <akpm <at> osdl.org> writes:

> Neil Brown <neilb <at> cse.unsw.edu.au> wrote:
> >
> > On Tuesday August 5, akpm <at> osdl.org wrote:
> > > Neil Brown <neilb <at> cse.unsw.edu.au> wrote:
> > > > ...
> > > > Aug  6 15:22:05 adams kernel: EXT3-fs error (device md1):
ext3_add_entry: bad entry in directory #41
> > > > 009295: rec_len is smaller than minimal - offset=0, inode=3265411686,
rec_len=0, name_len=0
> > >
> > > It looks like we had a block full of zeroes come back from the device
> > > driver.  I find it distinctly fishy how this happens so much with
> > > ext3-on-md, and so little with ext3-on-just-a-disk.
> >
> > Well, they're not *all* zero.....
> >
> > I can reproduce this easily with various configurations of ext3 over
> > raid5, and get a similar problem with ext2 over raid5 (corrupt inodes
> > rather than directory entries) but ext3 over raid0 is rock-solid.
>
> Good news that it is reproducible.

Has anything ever come out of this?

I am setting up a database server with RAID5, LVM2 and ext3fs, and has
just stumbled upon this issue.  Now I am nervous about proceeding.  If
there is a patch in some 2.6.3-rc I'd just upgrade, otherwise perhaps
I have to go back to 2.4.24?

I have seen people reporting this with 2.6.0 and 2.6.1 very recently,
nothing on 2.6.2 yet.  I took a look at the 2.6.2 ChangeLog, found
nothing that seemed relevant.


> Have you tried running fsx-linux?  It is good at picking up data loss.

I just finished memtest86 and cpuburn, nothing interesting.  Now how should I
run fsx-linux?  Perhaps I'm just tired, but I couldn't find any usage
information I was actually able to use.

I will continue to try, meanwhile any information either on the error itself or
on how to run fsx-linux is welcome.




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]