diff options
author | Mike Christie <michaelc@cs.wisc.edu> | 2008-08-19 18:45:31 -0500 |
---|---|---|
committer | James Bottomley <James.Bottomley@HansenPartnership.com> | 2008-10-13 09:28:52 -0400 |
commit | 4a27446f3e39b06c28d1c8e31d33a5340826ed5c (patch) | |
tree | e55c982632ab6e0a8484f8267fce8f159b6f78dc /drivers/scsi/lpfc/lpfc_els.c | |
parent | 6000a368cd8e6da1caf101411bdb494cd6fb8b09 (diff) | |
download | linux-stable-4a27446f3e39b06c28d1c8e31d33a5340826ed5c.tar.gz linux-stable-4a27446f3e39b06c28d1c8e31d33a5340826ed5c.tar.bz2 linux-stable-4a27446f3e39b06c28d1c8e31d33a5340826ed5c.zip |
[SCSI] modify scsi to handle new fail fast flags.
This checks the errors the scsi-ml determined were retryable
and returns if we should fast fail it based on the request
fail fast flags.
Without the patch, drivers like lpfc, qla2xxx and fcoe would return
DID_ERROR for what it determines is a temporary communication problem.
There is no loss of connectivity at that time and the driver thinks
that it would be fast to retry at the driver level. SCSI-ml will however
sees fast fail on the request and DID_ERROR and will fast fail the io.
This will then cause dm-multipath to fail the path and possibley switch
target controllers when we should be retrying at the scsi layer.
We also were fast failing device errors to dm multiapth when
unless the scsi_dh modules think otherwis we want to retry at
the scsi layer because multipath can only retry the IO like scsi
should have done. multipath is a little dumber though because it
does not what the error was for and assumes that it should fail
the paths.
Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
Diffstat (limited to 'drivers/scsi/lpfc/lpfc_els.c')
0 files changed, 0 insertions, 0 deletions