From: Chandra Seetharaman <sekharan@us.ibm.com>
To: "Chauhan, Vijay" <Vijay.Chauhan@lsi.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"'dm-devel@redhat.com'" <dm-devel@redhat.com>
Subject: RE: [PATCH]scsi_dh_rdac: Retry for NOT_READY check condition (0x02A102, 0x020401, 0x020404 and 0x020407) in rdac_check_sense
Date: Tue, 24 Mar 2009 12:38:29 -0700 [thread overview]
Message-ID: <1237923509.24723.0.camel@chandra-ubuntu> (raw)
In-Reply-To: <0D1E8821739E724A86F4D16902CE275C1410DBBA51@inbmail01.lsi.com>
On Tue, 2009-03-17 at 18:51 +0530, Chauhan, Vijay wrote:
> Hi James,
>
> Thanks for your comment. I have updated the patch with your comments.
>
> On Tues, 2009-03-10 21:17 +0530, James Bottomley wrote:
> > > + 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 == 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?
> >
> Yes, I do agree. Submitting patch for 0x02A102 only.
>
> Thanks,
> Vijay
>
> ---
> This patch adds retry for NOT_READY check condition - Quiescense in progress (02/A1/02)
>
> Signed-off-by: Vijay Chauhan<vijay.chauhan@lsi.com>
Acked-by: Chandra Seetharaman <sekharan@us.ibm.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-17 18:18:07.000000000 +0530
> @@ -562,6 +562,12 @@ 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;
> break;
> case ILLEGAL_REQUEST:
> if (sense_hdr->asc == 0x94 && sense_hdr->ascq == 0x01) {
> ----
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-03-24 19:35 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
2009-03-17 13:21 ` Chauhan, Vijay
2009-03-24 19:38 ` Chandra Seetharaman [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=1237923509.24723.0.camel@chandra-ubuntu \
--to=sekharan@us.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Vijay.Chauhan@lsi.com \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sekharan@linux.vnet.ibm.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