On Wednesday 12 December 2007 14:39:27 Matthew Wilcox wrote: > On Wed, Dec 12, 2007 at 01:54:14PM +0100, Bernd Schubert wrote: > > below is a patch introducing device recovery, trying to prevent i/o > > errors when a DID_NO_CONNECT or SOFT_ERROR does happen. > > Why doesn't the regular scsi_eh do what you need? First of all, it is presently simply not called when the two errors above do happen. This could be changed, of course. Secondly, I think scsi_eh is in most cases doing too much. We are fighting with flaky Infortrend boxes here, and scsi_eh sometimes manages to crash their scsi channels. In most cases it is sufficient to stall any io to the device and then to resume. For most scsi devices one probably doesn't need a suspend time or it can be very small, this still needs to become configurable via sysfs. Thirdly, scsi_eh doesn't give up, in most cases, when the scsi channel of a Infortrend box crashed, it tried forever to recover. To improve this is still on my todo list. Thanks, Bernd -- Bernd Schubert Q-Leap Networks GmbH - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
