Hi,
Documentation/scsi/scsi_mid_low_api.txt says:
resid - an LLD should set this signed integer to the ...
<snip>
underflow - LLD should place (DID_ERROR << 16) in 'result' if ...
<snip>
ZFCP is setting resid and DID_ERROR if an underrun is indicated in the
FCP-response.
In some error situations it occurs that the storage box reports a BUSY
or TASK_SET_FULL scsi state as well as data underrun in the
FCP-response.
Now zfcp sets DID_ERROR in host_byte as suggested in
scsi_mid_low_api.txt. And the BUSY/TASK_SET_FULL state is returned in
stauts_byte.
Problem is:
Due to the its fastfail-operation the scsi-stack won't do any
retry for this kind of failed commands because DID_ERROR is
evaluated before BUSY/TASK_SET_FULL.
What is the proper handling of situations where the device reports a
BUSY/TASK_SET_FULL and a data underrun?
Regards,
Andreas
-
: 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
