Just to clarify - two logins for was what you call "Provision 2x LUNs from VNX". AFAIK the LUNZ is a representation of "what could be" and once provisioned that is replaced by "the real thing". Since in my example that matches an FCP SAN login I might have named it badly for you to realize what I meant - sorry.
Thank you for providing the sq_inq data. So it really seems multipathd has some stale data from the former /dev/sd* devices. You said "then rescan SCSI bus to reflect the changes" - since there seem to be multiple ways to do so might I ask what you did in your case to do so? For the lifetime of that stale data I wanted to ask, if you are in the error case, does one of the following get you back to a good state with all detected as VRAID and multipath set up? $ service multipathd reload or $ service multipathd restart -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671397 Title: A VNX LUN will still be recognized as LUNZ after provisioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1671397/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
