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? What is the use case for an initiator needing a lu available via more than 1 lun? 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? Regards -- Andy -- 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
