Re: use case for multiple mapped LUNs?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2012-07-11 at 11:22 -0700, Andy Grover wrote:
> Hi all,
> 
> As Gris brings up here:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=838759
> 
> do we also want to disallow (or at least warn) when the user attempts to
> map a storageobject to an initiator more than once?

I would definately go for a warn over a fail.

>  What is the use case
> for an initiator needing a lu available via more than 1 lun?

Not a type customer case, but useful for testing multipath on the same
session if no more HW ports are available.

>  The only
> parameter difference is write_protect=rw or ro and lu number, should we
> disallow if write_protect and base lu matches an existing mapping? Thoughts?
> 

Leaning to warning over fail for this particular user ex scenario (jxm
CC'ed)

Thanks Andy!

--nab





--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux