From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Chauhan, Vijay" <Vijay.Chauhan@lsi.com>
Cc: "'dm-devel@redhat.com'" <dm-devel@redhat.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH]scsi_dh_rdac: Retry for NOT_READY check condition (0x02A102, 0x020401, 0x020404 and 0x020407) in rdac_check_sense
Date: Tue, 10 Mar 2009 10:46:31 -0500 [thread overview]
Message-ID: <1236699991.14822.0.camel@localhost.localdomain> (raw)
In-Reply-To: <0D1E8821739E724A86F4D16902CE275C140E25CA0C@inbmail01.lsi.com>
On Tue, 2009-03-10 at 18:30 +0530, Chauhan, Vijay wrote:
> This patch adds retry for NOT_READY check conditions(02/A1/02, 02/04/01, 02/04/04,
> 02/04/07) in rdac_check_sense.
>
> Signed-off-by: Vijay Chauhan<vijay.chauhan@lsi.com>
>
> ---
> --- linux-2.6.29-rc7/drivers/scsi/device_handler/scsi_dh_rdac.c.orig 2009-03-10 17:42:27.000000000 +0530
> +++ linux-2.6.29-rc7/drivers/scsi/device_handler/scsi_dh_rdac.c 2009-03-10 18:05:35.000000000 +0530
> @@ -562,6 +562,30 @@ static int rdac_check_sense(struct scsi_
> * Just retry and wait.
> */
> return ADD_TO_MLQUEUE;
> + if (sense_hdr->asc == 0xA1 && sense_hdr->ascq == 0x02)
> + /* LUN Not Ready - Quiescense in progress
> + * or has been achieved
> + * Just retry.
> + */
> + return ADD_TO_MLQUEUE;
This is fine, being vendor specific, we don't handle it at the mid-layer
> + if (sense_hdr->asc == 0x04 && sense_hdr->ascq == 0x01)
> + /* LUN Not Ready - Logical Unit Not Ready and is in
> + * the process of becoming ready
> + * Just retry.
> + */
> + return ADD_TO_MLQUEUE;
> + if (sense_hdr->asc == 0x04 && sense_hdr->ascq == 0x04)
> + /* LUN Not Ready - Format In Progress
> + *
> + * Just retry.
> + */
> + return ADD_TO_MLQUEUE;
> + if (sense_hdr->asc == 0x04 && sense_hdr->ascq == 0x07)
> + /* LUN Not Ready - Storage controller cannot respond
> + * immediately to a PRIN or PROUT command.
> + * Just retry.
> + */
> + return ADD_TO_MLQUEUE;
For all of these ... along with a few other not ready types, we already
do a delayed retry at the mid-layer (in scsi_io_completion). Is there
some problem that causes this to need to be handled here as well?
James
next prev parent reply other threads:[~2009-03-10 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 13:00 [PATCH]scsi_dh_rdac: Retry for NOT_READY check condition (0x02A102, 0x020401, 0x020404 and 0x020407) in rdac_check_sense Chauhan, Vijay
2009-03-10 15:26 ` Hannes Reinecke
2009-03-10 15:46 ` James Bottomley [this message]
2009-03-17 13:21 ` Chauhan, Vijay
2009-03-24 19:38 ` Chandra Seetharaman
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=1236699991.14822.0.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Vijay.Chauhan@lsi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox