Re: Ext3 errors with 2.4.18
Andreas Dilger (adilger@clusterfs.com)
Tue, 14 May 2002 04:49:22 -0600
On May 14, 2002 12:38 +0200, Oliver Feiler wrote:
> On Monday 06 May 2002 18:25, Udo A. Steinberg wrote:
> > Hi,
> >
> > With Linux 2.4.18, I'm getting multiple of the following error:
> >
> > EXT3-fs error (device ide0(3,2)): ext3_readdir: bad entry in directory
> > #1966094: rec_len % 4 != 0 - offset=0, inode=3180611420, rec_len=53134,
> > name_len=138
>
> Hi,
>
> I experienced the same problem with ext3 + 2.4.18 on a RAID-1. Out of nowhere
> the following error popped up in the syslog, no other surrounding error
> messages. The fs was mounted read-only automatically. After reboot and fsck
> there were /a lot/ of errors on the disk. Virtually all errors fsck knows I
> think. :) After fsck ran multiple times on the disk, lost+found was filled
> with stuff from all accross the disk, but other than that the fs seems to
> have survived it.
There have been several reports of strange ext3 errors when running on
MD RAID. I don't know if anyone is looking into this yet.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
-
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/