> Linux 2.2.1, K6-233, NCR815, no signs of trouble with the disk (IBM
> DCAS) or memory so far.
>
> Feb 11 06:42:05 bigred kernel: EXT2-fs warning (device 08:01): ext2_free_inode:
> bit already cleared for inode 3836
> Feb 11 06:44:22 bigred kernel: attempt to access beyond end of device
> Feb 11 06:44:22 bigred kernel: 08:01: rw=0, want=167772158, limit=41509
> Feb 11 06:44:22 bigred kernel: EXT2-fs error (device 08:01): ext2_readdir: directory #4025 contains a hole at offset 0
> Feb 11 06:44:22 bigred kernel: attempt to access beyond end of device
> Feb 11 06:44:22 bigred kernel: 08:01: rw=0, want=473270776, limit=41509
>
> Then the system crashed and was rebooted (perhaps by softdog). The
> partition on 08:01 showed severe damage (lots of "entry has
> deleted/invalid inode" type errors, luckily mostly for /dev entries).
>
> Other system logs tell the type of activity on the filesystem:
I have seen exactly this happening in 2.0.36 on two or more machines
and several times. Both SCSI and EIDE discs were affected. As you say - it
generated quite lot of damage to fs. I have been suspecting a bug in
ext2fs code, but never came up with anything (couldn't reproduce it etc.)
Bye Borek
--===================================================================== BOREK LUPOMESKY, network administrator University of J. E. Purkyne WWW: http://www.ujep.cz/~lupomesk/ Ceske mladeze 8 IRCnet: Borek @ #usti Usti nad Labem, 40012 talk: borek@ishtar.ujep.cz The Czech Republic PGP keyid: 9DD1C54D tel: +420-602-376368 ==========[ MIME/ISO-8859-2 & PGP encrypted mail welcome ]===========
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/