Hi,
On Thu, 17 Feb 2000 15:42:29 -0500 (EST), Mike Porter <mike@UDel.Edu>
said:
> I have seen one occurance of this on my machine - dual Pentium IIIs.
> 2.3.43.
> ls <file-name> would list the file.
> ls -l <file-name> would generate an I/O error, as would any other
> attempt to open the file.
> Rebooted a day or two later (after my first occurance of seeing the
> missing interrupt for /dev/hda for the first time ever - system
> would not recover). fsck reported a bad/unused inode.
That looks exactly like what I'd expect to see if the disk returned a
bad block in the middle of an inode table. In particular, the
filesystem is correctly returning a clean EIO error to the application
rather than getting itself tied up in knots over the error.
Looks like the kernel was working perfectly here...
--Stephen
-
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/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:22 EST