Hannes Reinecke wrote:
/*
+ * Evaluate scsi return code
+ */
+static int eval_scsi_error(int result, char *sense, int sense_len)
+{
+ struct scsi_sense_hdr sshdr;
+ int r = DM_ENDIO_REQUEUE;
+
+ if (host_byte(result) != DID_OK)
For values like DID_NO_CONNECT or DID_TRANSPORT FAILFAST, I think it
makes sense to fail the path. Not in this patch, but a new one, would we
want to modify dm-mpath so that we do not fail the path for errors like
DID_ABORT or DID_SOFT_ERROR, DID_RESET or DID_ERROR?
--
To unsubscribe from this list: 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
