> In general, wacking the SCSI with bus resets to abort I/O may
> do the trick, but it's not nice to affect all devices because of say
> a timeout on a single device In our CAM implementation, we first try
> an Abort, then BDR, then BR as a last resort (well actually, reloading
> firmware is the last resort on some adapters).
This is actually the same strategy used by Linux. The implementation
may have warts here and there, but we essentially go through the same
sequence. In practice some drivers may not correctly implement the
functionality to perform some of these actions.
I should also point out that most low-level drivers still use the old
error handling code, and it has been known for years that the old error
handling code was substandard. I have pleaded off and on since I first
introduced the new error handler for people to convert their drivers, but
unfortunately only a handful of the drivers have been converted. Once the
2.5 kernel series gets started, I am going to completely nuke the old error
handling code. This will of course break about 80% of the low-level drivers
out there which will force the maintainers to *finally* update the drivers.
-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
