All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Michael Christie <michaelc@cs.wisc.edu>
Cc: linux-scsi@vger.kernel.org, James Bottomley <jbottomley@parallels.com>
Subject: Re: [PATCH] scsi: return TARGET_ERROR when a device has been disconnected
Date: Thu, 16 Aug 2012 16:59:10 +0200	[thread overview]
Message-ID: <502D0ABE.1010709@suse.de> (raw)
In-Reply-To: <AF371CF6-F10B-470D-810E-4C1F42057E79@cs.wisc.edu>

On 08/16/2012 04:53 PM, Michael Christie wrote:
> 
> On Aug 16, 2012, at 1:40 AM, Hannes Reinecke <hare@suse.de> wrote:
> 
>> When we receive a sense code of
>> NOT READY, LOGICAL UNIT NOT SUPPORTED
>> the device has been disconnected and any retry on other paths
>> would be pointless. So return TARGET_ERROR here.
> 
> 
> What target is this with?

HP EVA.

> What about {ILLEGAL_REQUEST,  LOGICAL UNIT NOT SUPPORTED}?
> Would you want to do the same behavior for that error?
> 
Yes, presumably.

> I ask because I have seen targets return {ILLEGAL_REQUEST,  LOGICAL UNIT NOT SUPPORTED}
> when you only unexport the LUN from a path/port on the target.
> I was wondering if some might do the same for {NOT_READY, LOGICAL
UNIT NOT SUPPORTED}?
> In those cases, we would not want multipath to fail IO.
> 
That's exactly the use-case. When you unexport a target you're
getting the "LUN NOT SUPPORTED" message. And you'll need to return
the error to the upper layers, as you might want to disconnect the
device (eg do a 'rescan-scsi-bus.sh') and you'll want to finish any
program quickly here.

> In these type of cases should the target be returning something else?
> 
No, that's okay.
We should be modifying it to encompass both.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)


--
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

      reply	other threads:[~2012-08-16 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16  6:40 [PATCH] scsi: return TARGET_ERROR when a device has been disconnected Hannes Reinecke
2012-08-16 14:53 ` Michael Christie
2012-08-16 14:59   ` Hannes Reinecke [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=502D0ABE.1010709@suse.de \
    --to=hare@suse.de \
    --cc=jbottomley@parallels.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    /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.