On Wed, Mar 29, 2017 at 11:22:42PM +0200, Martin Wilck wrote: > On Tue, 2017-03-28 at 11:42 -0500, Benjamin Marzinski wrote: > > > Now the question is, what to we do if the path changes wwid, but it's > > not part of a multipath device yet. We could simply print a warning > > message that the wwid has changed, and allow it to happen, since > > there's > > no multipath device currently using the LUN. However, I have seen > > cases > > where multiple LUNs that have already been discovered by a node get > > unmapped, and all the unmapped LUNs from a device get the same > > ID_SERIAL > > value in the uevent for the mapping change. This would cause > > find_multipaths to create a multipath device that includes all of > > these > > unmapped devices, which is clearly wrong. > > and in that siutation there'd be no way to detect that these are > unmapped LUNs which don't qualify as paths for a multipath device? Not really. They fail every checker function, but we don't check paths that aren't being used. Otherwise, all the sysfs parameters stay the same, and there's nothing special in the uevent. Discovered LUNs shouldn't be getting remapped in general. The kernel spits out an warning message, saying that this isn't handled. -Ben > > Regards > Martin > > -- > Dr. Martin Wilck <mwilck@xxxxxxxx>, Tel. +49 (0)911 74053 2107 > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton > HRB 21284 (AG Nürnberg) > > -- > dm-devel mailing list > dm-devel@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/dm-devel -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
