path: root/block
diff options
authorMike Christie <>2011-08-25 00:36:38 -0500
committerJames Bottomley <>2011-08-29 00:16:19 -0700
commit76e4e12ff2b3ef86773989fd897b194eb38016e6 (patch)
tree26db91684e2d70db0d5ff2022e48bc8230fe6f8d /block
parenteccdcd026ae7359e22b70444b8a45f712f05cc37 (diff)
[SCSI] scsi scan: don't fail scans when host is in recovery
The problem is that if we are doing a scsi scan then the device goes into recovery then we will wait for the recovery to complete. It waits because scsi-ml will send inquiries or report luns and the queueing code will have been blocked due to the host not being ready. However, if we are in recovery and then a scan is started the scan will silently fail and some devices will not be added. It is easy to hit the problem where devices do not show up with FC where we are doing tests that disrupt the target controllers. When the controller is disruprted (reboot, or setting firmware, etc), and we cause the dev loss tmo to fire then devices will be removed Then when the problem has been fixed, the rport will be scanned and devices should be added back. But if we cause another disruption before scanning has started then devices will not get added back. If the problem is not started until the scan is started then the devices will be added back. This patch fixes that problem by not failing scans when the host is in recovery. We will let scsi-ml send the IO and let the queueing and scsi error handling deal with it like is done if we went into recovery while scanning. For recovery cases where the host is being torn down then with the patch we will still fail the scan since there is not point in scanning. Signed-off-by: Mike Christie <> Signed-off-by: James Bottomley <>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions