summaryrefslogtreecommitdiffstats
path: root/REPORTING-BUGS
diff options
context:
space:
mode:
authorAlan Stern <stern@rowland.harvard.edu>2005-03-30 15:05:45 -0500
committerJames Bottomley <jejb@mulgrave.(none)>2005-09-06 17:19:23 -0500
commite47373ec1c9aab9ee134f4e2b8249957e9f4c7ef (patch)
treee6f630c08223f71d1cbb502213503404ec65d86f /REPORTING-BUGS
parent4dddbc26c3895ecdab1f4b16435685b47f96f599 (diff)
downloadop-kernel-dev-e47373ec1c9aab9ee134f4e2b8249957e9f4c7ef.zip
op-kernel-dev-e47373ec1c9aab9ee134f4e2b8249957e9f4c7ef.tar.gz
[SCSI] return success after retries in scsi_eh_tur
The problem lies in the way the error handler uses TEST UNIT READY to tell whether error recovery has succeeded. The scsi_eh_tur function gives up after one round of retrying; after that it decides that more error recovery is needed. However TUR is liable to report sense data indicating a retry is needed when in fact error recovery has succeeded. A typical example might be SK=2, ASC=4, ASCQ=1 (Logical unit in process of becoming ready). The mere fact that we were able to get a sensible reply to the TUR should indicate that the device is working well enough to stop error recovery. I ran across a case back in January where this happened. A CD-ROM drive timed out the INQUIRY command, and a device reset fixed the blockage. But then the drive kept responding with 2/4/1 -- because it was spinning up I suppose -- until the error handler gave up and placed it offline. If the initial INQUIRY had received the 2/4/1 instead, everything would have worked okay. It doesn't seem reasonable for things to fail just because the error handler had started running. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
Diffstat (limited to 'REPORTING-BUGS')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud