From: Mike Christie <michaelc@cs.wisc.edu>
To: device-mapper development <dm-devel@redhat.com>
Cc: James Bottomley <James.Bottomley@suse.de>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] multipath: Evaluate request result and sense code
Date: Sun, 22 Nov 2009 15:00:17 -0600 [thread overview]
Message-ID: <4B09A661.10102@cs.wisc.edu> (raw)
In-Reply-To: <20091119122503.413AD3A174@ochil.suse.de>
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?
next prev parent reply other threads:[~2009-11-22 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 12:25 [PATCH] multipath: Evaluate request result and sense code Hannes Reinecke
2009-11-19 19:58 ` Mike Christie
2009-11-20 7:48 ` [dm-devel] " Hannes Reinecke
2009-11-22 20:47 ` Mike Christie
2009-11-22 21:00 ` Mike Christie [this message]
2009-11-26 7:54 ` [dm-devel] " Hannes Reinecke
2009-11-26 0:25 ` Moger, Babu
2009-11-26 8:03 ` Hannes Reinecke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B09A661.10102@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@suse.de \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.