Device 08:11 not ready.
I/O error: dev 08:11, sector 26908624
Device 08:11 not ready.
I/O error: dev 08:11, sector 121208
Device 08:11 not ready.
I/O error: dev 08:11, sector 26908624
Device 08:11 not ready.
I/O error: dev 08:11, sector 278936
vs-13050: reiserfs_update_sd: i/o failure occurred trying to update [487
175497 0x0 SD] stat data<6>Device 08:11 not ready.
I/O error: dev 08:11, sector 75432
vs-13050: reiserfs_update_sd: i/o failure occurred trying to update [260
487 0x0 SD] stat data<6>Device 08:11 not ready.
I/O error: dev 08:11, sector 65680
journal-712: buffer write failed
kernel BUG at prints.c:332!
Basically, one of the server's drives (not the root one, though) stopped
responding. It seems better after a power cycle, but it definately
appeared to be a hardware problem.
My issue, though, is Linux did not handle it well. Userspace actually has
an 'EIO' error code for this situation but, instead, any program touching
the mounted partition hung in a D state.
You can't kill the processes; you can't unmount the partition; you
consequently can't reboot the box in any normal manner. The box was in a
pretty broken, unusable state.
Is it possible for the kernel to handle this with enough grace that you
can kill the processes and unmount the partition? (Thus allowing the box
to continue in a hobbled, but function manner.) Failing that, is it
possible for the kernel to handle it well enough for 'shutdown' to cleanly
shutdown the box?
Thank you
-- Brian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Sep 23 2001 - 21:00:18 EST