Re: different LUN numbers under the same dm device

[Hannes Reinecke <hare@suse.de>]

(Third mail on this topic .. I really should've read the entire
thread before answering. But there you go.)

On 06/08/2012 01:26 AM, Brian Bunker wrote:
> The answer is yes they did have that LUN NAA value that comes from page code 0x83 in inquiry.
> Then the LUN was unmasked from that initiator. That initiator is
holding on to those device
> names in multipath. If you query them when they are in the state
that I show in the
> multipath -ll result, they will not return an NAA number at all in
page code 0x83 or
> a serial number in page code 0x80. They will instead return a PQ
of 1 meaning that the
> LUN is capable of supporting a peripheral device but is not currently.
> 
Hehe.

> I understand about LUN's needing different NAA numbers and ours do, and we also have
> different LUN serial numbers for each LUN on the target. An
initiator doesn't always
> have to access to all LUN's that it once did. It is the re-use of
dm devices that
> seems to cause this result.
> 
No, rather a problem with the SCSI stack. multipath normally relies
on udev to keep track of any device events, like LUNs coming and
going. But this only works reliably if these events are triggered
via the underlying transport, like FC RSCN et al.

'Real' scsi events which will get transmitted via Sense codes are
not evaluated further, sadly.

So short-term you are supposed to call 'rescan-scsi-bus.sh -r'
whenever you made any LUN assigment changes on the array.
Mid-term we already agreed on implementing some proper sense code
handling in the SCSI midlayer.
However, as usual in these cases, real life interfered and I've been
busy with other things.
But it's definitely on the agenda.

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)