On 08/16/2012 04:53 PM, Michael Christie wrote:
>
> On Aug 16, 2012, at 1:40 AM, Hannes Reinecke <hare@xxxxxxx> 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@xxxxxxx +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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
