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

Re: Bad directories appearing in ext3 after upgrade 2.4.16 -> 2.4.18+cvs



On May 21, 2002  16:30 +1000, Neil Brown wrote:
>  I recently upgraded one of my fileservers from 2.4.16 to 2.4.18 plus
>  the ext3-cvs.patch that Andrew Morton pointed me to for addressing
>  and assertion failure.
> 
>  Since then I have been getting lots of errors like:
> 
> May 21 14:07:03 glass kernel: EXT3-fs error (device md(9,0)): ext3_add_entry: bad entry in directory #2945366: rec_len %% 4 != 0 - offset=0, inode=1886221359, rec_len=24927, name_len=109
> May 21 14:07:23 glass kernel: EXT3-fs error (device md(9,0)): ext3_readdir: bad entry in directory #2945366: rec_len %% 4 != 0 - offset=0, inode=1886221359, rec_len=24927, name_len=109
> May 21 14:07:23 glass kernel: EXT3-fs warning (device md(9,0)): empty_dir: bad directory (dir #2945366) - no `.' or `..'

>  But I wonder if anyone else has this or has any idea what it might be?

Well, there were several recent reports of ext3 problems, and two
reports had the same message.  Two of them definitely were also using
RAID (RAID 1 and RAID 5).

See thread starting at:
http://marc.theaimsgroup.com/?l=linux-kernel&m=102070252100762&w=4

and also an older (but still 2.4.18) thread at:
http://marc.theaimsgroup.com/?l=ext3-users&m=101041709332435&w=4

No mention of RAID in the second thread.  I can't find the other
messages to which I refer in the first thread about "several other
reports of corruption with ext3 on MD RAID".

Neil, you posted in another message the text from the corrupt directory
blocks, which matches with the second thread where the bad data looked
like filenames (the first thread's directory data doesn't decode to
anything useful in ASCII).

Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/





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