Messages in this thread | | | Date | Sat, 24 Jan 1998 18:06:04 +0100 (MET) | From | Andries.Brouwer@cwi ... | Subject | ext2 corruption in 2.0.33 |
| |
Below a report on ext2 corruption I got a moment ago. If noone else reports such things[*] then maybe my hardware is not 100%, but this is a 1-month-old machine that has never given any cause for suspicion. For the time being I suspect the kernel, a vanilla 2.0.33.
[*] It is a pity that linux.kernel is unavailable as a newsgroup. It is far too much to read as mail. So, I am afraid I have no idea whether this is an isolated occurrence.
The report:
Unpack linux-2.1.81.tar.gz, make config, make depend, and cpp: ip_gre.c: Input/output error Strange ... The kernel log complains Jan 24 15:33:53: attempt to access beyond end of device Jan 24 15:33:53: 08:12: rw=0, want=707725610, limit=2048000 Jan 24 15:33:53: attempt to access beyond end of device Jan 24 15:33:53: 08:12: rw=0, want=2019642657, limit=2048000 Jan 24 15:33:53: attempt to access beyond end of device e2fsck comes with a similar message: Illegal block #12 (707725609) in inode 131360. CLEARED. Illegal block #13 (2019642656) in inode 131360. CLEARED. Illegal block #14 (1836412265) in inode 131360. CLEARED.
These strange numbers really look like text... Printing them (the e2fsck ones) as bytes yields ) /* Maximum allowed timeout */ /* IP confi in other words, a fragment of the file net/ipv4/ipconfig.c was written here.
Andries
| |