Re: FS corruption still in 2.2.13
Miquel van Smoorenburg (miquels@cistron.nl)
22 Oct 1999 12:42:10 +0200
In article <cistron.Pine.BSI.4.05L.9910220715570.26526-100000@unit11.support.nl>,
Tommy van Leeuwen <tommy@support.nl> wrote:
>This week i posted a report of fs corruption in 2.2.12. People asked me
>if i also got the error with the 2.2.13pre patches. I switched to
>2.2.13 yesterday and the fs corruption is reoccuring.
>
>This is what i get now:
>
>Oct 21 23:13:04 news2 kernel: EXT2-fs error (device md(9,3)):
>ext2_add_entry: bad entry in directory #10022921: directory entry across
>blocks - offset=7152, inode=843004500, rec_len=17248, name_len=45
>Oct 21 23:13:04 news2 kernel: EXT2-fs error (device md(9,3)):
>ext2_add_entry: bad entry in directory #10022921: directory entry across
>blocks - offset=7152, inode=843004500, rec_len=17248, name_len=45
I've seen this before - in all cases it was a bad SCSI controller, a
bad cable (or bad cabling, termination!) or bad memory.
Mike.
--
First things first, but not necessarily in that order.
-
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/