Re:ext2fs corruption

Joerg Diederich (
Fri, 15 May 1998 09:22:18 +0200 (MET DST)

>May 13 00:09:27 citadel kernel: EXT2-fs warning (device 03:03):
>ext2_free_inode: bit already cleared for inode 2066
>May 13 00:09:51 citadel kernel: EXT2-fs warning (device 03:03):
>ext2_free_inode: bit already cleared for inode 2291
>May 13 00:12:06 citadel kernel: EXT2-fs warning (device 03:03):
>empty_dir: bad directory (dir #2113) - no `.' or `..'

I saw this yesterday as well. After I had run e2fsck, some files where
corrupted severely (very strange flags and user / group id). I was neither
able to delete the files (permission denied) nor change the flags so that
I had to run debugfs to delete them (e2fsck didn't help anymore).

I also got DMA timeouts and such things. In fact, I cannot give more
detailed information as I thought this error occured because of my
changings in the bios settings (played around a little :-) so I didn't
store any message).
After I removed the bios settings and ran debugfs, everything was
fine again (but of course I could not test much since yesterday evening).

My Setup:

Linux 2.1.97
Cyrix MX-PR200 (75Mhz Clock, but PCI Clock 33MHz (async))
Gigabyte GA586 STX (Sis 5582)
hda: IBM 4.3GB
hdc: nec 12x cdrom

(Busmastering enabled)

As I got the DMA timeouts mainly when using my TV-tuner card (Bt848),
there also could be some error in it (and this could also be the reason
for the damage of the file system, as my tuner card showed very strange
behaviour when I last used it).

I think I will for now watch the whole thing a while to see if the error
occures again.

I hope this mail helps you anyway.

Joerg Diederich

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to