Re: ext2 bug

Jon Lewis (jlewis@inorganic5.fdt.net)
Fri, 31 May 1996 20:07:41 -0400 (EDT)


On Fri, 31 May 1996, Gerd Knorr wrote:

> May 31 21:06:28 felix kernel: EXT2-fs error (device 08:16): ext2_readdir:
> bad entry in directory #65283: rec_len is too small for name_len -
> offset=36, inode=65299, rec_len=16, name_len=136
> May 31 21:06:35 felix kernel: EXT2-fs error (device 08:16): ext2_readdir:
> bad entry in directory #65283: rec_len is too small for name_len -
> offset=36, inode=65299, rec_len=16, name_len=136
> May 31 21:06:38 felix kernel: EXT2-fs error (device 08:16):
> ext2_find_entry: bad entry in directory #65283: rec_len is too small for
> name_len - offset=36, inode=65299, rec_len=16, name_len=136
> May 31 21:06:38 felix last message repeated 4 times
>
> running kernel is 1.99.8, hd is a 1 GB scsi attaced to a aha1542

I get quite similar things every few days on my news server (1.2.13, NCR
810, rel16 driver). I'd been blaming it on the NCR driver. Is it
possible that it's actually a fs bug? umounting the offending partition
and running e2fsck -fy generally fixes things for a while.

------------------------------------------------------------------
Jon Lewis | Mime attachments are OK
jlewis@inorganic5.fdt.net | But please ask before sending
http://inorganic5.fdt.net | unsolicited huge files.
________Finger jlewis@inorganic5.fdt.net for PGP public key_______