From: Christophe Varoqui <christophe.varoqui@gmail.com>
To: "Moger, Babu" <Babu.Moger@netapp.com>
Cc: dm-devel <dm-devel@redhat.com>
Subject: Re: [PATCH] multipath: retry the DID_SOFT_ERROR for rdac checker commands
Date: Wed, 11 Jul 2012 10:05:23 +0200 [thread overview]
Message-ID: <1341993923.23291.0.camel@lapoo.opensvc.com> (raw)
In-Reply-To: <77471C95FAFD844C8CA02DD4F4C5FE2B07E5F4B9@SACEXCMBX02-PRD.hq.netapp.com>
On mar., 2012-07-10 at 19:12 +0000, Moger, Babu wrote:
> Sometimes we have seen immediate path failures for DID_SOFT_ERROR status. Just add a retry as other statuses.
> It will basically add 5 retries.
>
Applied.
Thanks.
> Here are the messages.
> Jun 4 17:46:42 ictc-billy kernel: mpt2sas0: log_info(0x31120100): originator(PL), code(0x12), sub_code(0x0100)
> Jun 4 17:46:42 ictc-billy kernel: sd 1:0:0:47: [sdn] Unhandled error code
> Jun 4 17:46:42 ictc-billy kernel: sd 1:0:0:47: [sdn] Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK
> Jun 4 17:46:42 ictc-billy kernel: sd 1:0:0:47: [sdn] CDB: Write(10): 2a 00 00 06 e4 a0 00 00 20 00
> Jun 4 17:46:42 ictc-billy kernel: device-mapper: multipath: Failing path 8:208.
> Jun 4 17:46:42 ictc-billy multipathd: 8:208: mark as failed
> Jun 4 17:46:42 ictc-billy multipathd: mpathat: remaining active paths: 1
>
>
> Signed-off-by: Babu Moger <babu.moger@netapp.com>
> ---
> --- multipath-tools/libmultipath/checkers/rdac.c.orig 2012-07-10 13:35:34.000000000 -0500
> +++ multipath-tools/libmultipath/checkers/rdac.c 2012-07-10 13:36:07.000000000 -0500
> @@ -166,6 +166,7 @@ retry:
> switch (io_hdr.host_status) {
> case DID_BUS_BUSY:
> case DID_ERROR:
> + case DID_SOFT_ERROR:
> case DID_TRANSPORT_DISRUPTED:
> /* Transport error, retry */
> if (--retry_rdac)
>
>
prev parent reply other threads:[~2012-07-11 8:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 19:12 [PATCH] multipath: retry the DID_SOFT_ERROR for rdac checker commands Moger, Babu
2012-07-11 8:05 ` Christophe Varoqui [this message]
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=1341993923.23291.0.camel@lapoo.opensvc.com \
--to=christophe.varoqui@gmail.com \
--cc=Babu.Moger@netapp.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).