diff options
author | Hannes Reinecke <hare@suse.de> | 2011-01-18 10:13:11 +0100 |
---|---|---|
committer | James Bottomley <James.Bottomley@suse.de> | 2011-02-12 17:33:08 +0100 |
commit | 63583cca745f440167bf27877182dc13e19d4bcf (patch) | |
tree | c1eb3ec5d35cd71c6373e82992710c91f2cb8bdd /samples | |
parent | [SCSI] scsi_dh_hp_sw: fix deadlock in start_stop_endio (diff) | |
download | linux-63583cca745f440167bf27877182dc13e19d4bcf.tar.xz linux-63583cca745f440167bf27877182dc13e19d4bcf.zip |
[SCSI] Add detailed SCSI I/O errors
Instead of just passing 'EIO' for any I/O error we should be
notifying the upper layers with more details about the cause
of this error.
Update the possible I/O errors to:
- ENOLINK: Link failure between host and target
- EIO: Retryable I/O error
- EREMOTEIO: Non-retryable I/O error
- EBADE: I/O error restricted to the I_T_L nexus
'Retryable' in this context means that an I/O error _might_ be
restricted to the I_T_L nexus (vulgo: path), so retrying on another
nexus / path might succeed.
'Non-retryable' in general refers to a target failure, so this
error will always be generated regardless of the I_T_L nexus
it was send on.
I/O errors restricted to the I_T_L nexus might be retried
on another nexus / path, but they should _not_ be queued
if no paths are available.
Signed-off-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions