------- Comment From mauri...@br.ibm.com 2016-03-14 18:08 EDT------- (In reply to comment #6) > I've triaged this bug, but it's quite very late in the cycle to ship new > features, especially one such as this one which appears to be mostly just a > convenient way of adding WWIDs to the multipath list.
Interestingly I forgot the point in time we are currently. Yes, indeed, it's just a convenient way of adding WWIDs, however, its importance lies if Ubuntu wants to enable its users to install multipath-tools-boot (say, in a LVM/multipath scenario) to boot from multipath. If the root fs is locked due to a LVM volume, it cannot be multipathed, thus its WWID won't be added to the list. During boot, the only chance for the LVM volume to be mounted from the multipath device is if the WWID is present (so the udev rule which removes the partition block devices from individual paths can succeed). So it's now a chicken and egg problem. You need to boot from multipath in order to be able to multipath the device with the root fs LVM LV. :-) With multipath -a, you can just install multipath-tools-boot, multipath -a /dev/sdX, update-initramfs -u; done. Without it, well, you can replace multipath -a for some multipath -v3 /dev/sdX | grep 'uid =' | sed/awk >> /etc/multipath/wwids.. but you see, it doesn't look quite 'this is how it should be done'. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1556967 Title: Support 'multipath -a' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1556967/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
