My two-cents worth: There is an Error Recovery problem in SCSI-land.
A serious one. Certain failures would cause the system to freeze.
Most HBA drivers do not recover very grwcefuly from hardware failures.
The SCSI tape code locks up devices upon failure and refuses to release
the calling process for what appears to be eternity.
Thanx Linus for the inclusion of MD! Are we still to approach his Majesty
with a ``Yes Master!''?
Also I have a case where a corrupted disk messed up ext2 file system in such
a way that fsck is very happy, but tar or cpio of a given directory just
freezes the system. No other clue :-(
Oh, Also, if an nfs server disapears, the client gets very confused.
Typically it will express itself as a hung telnet server. Don't ask...
There is a bigger issue of boot floppies, modules, on-line configuration,
but we will leave that to 1.5. Right?
Sincerely Yours,
(Sent on 02/29/96, 08:22:15)
Simon Shapiro i-Connect.Net, a Division of iConnect Corp.
Shimon@i-Connect.Net 13455 SW Allen Blvd., Suite 140 Beaverton OR 97008