Requiring a hwtable entry for a dm target device?

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

 



Currently a dm target device which is not blacklisted need not have a
corresponding hwentry in either libmultipath/hwtable.c or
/etc/multipath.conf
for the target device to be recognized and a multipath mapped device
created for it.  Is this desirable, possibly for multipathing to JBOD?

An alternative is to require that a hwentry be found and fail to recognize
the target device otherwise.  Doing so has the distinct advantage of being
able to use the regular expression matching logic in find_hwe() to
effectively
blacklist a target device based on the contents of the target device's
vendor
and product device attributes.

--

dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel

[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux