[Bug 1178721] Re: multipathd fails to create mappings when multipath.conf is present
** Changed in: multipath-tools (Ubuntu) Status: Triaged = Invalid -- 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/1178721 Title: multipathd fails to create mappings when multipath.conf is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+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
Re: [Bug 1178721] Re: multipathd fails to create mappings when multipath.conf is present
At this point I would seriously consider obtaining commercial support. This is clearly a support issue and not a bug and has been closed as invalid. LVM could have easier to grok filtering but it does work, you just have to get creative by changing the scan directory. For example: UNTESTED scan = [ /dev/mapper] filter = [ a|^/dev/mapper/mpath.*|, r/.*/ ] pvscan -vvv is your friend. Concerning your other SAN question, please seek professional support or seek forums (google) where SAN admins gather. We can't know how to configure *every single SAN on the market*. Again, LVM multipath are distro agnostic, *any other distro doc will do*. e.g. https://access.redhat.com/site/documentation/en- US/Red_Hat_Enterprise_Linux/5/html/Logical_Volume_Manager_Administration/lvm_filters.html On 06/10/2013 03:33 PM, Jernej Jakob wrote: Thank you for your help. I wasn't aware of the limitation (incompatibility) caused by co-deploying LVM and multipath, it was my assumption that multipath would be configured to take precedence over LVM for having PVs on multipath block devices, as having it the other way around, as in multiple paths over LVM logical volumes would not make sense. I can assume that this would be a pretty common scenario, as for example, you may have one volume mapped from SAN over FC on which the tools that LVM offers would be valuable. It would seem that a simple check at boot time, checking whether LVM and multipath are co-deployed, starting multipath first, letting it create paths and then adding those found to LVM's filter. I understand however that this is in no way common usage and requires a skillful enough administrator to be aware of the possible scenarios caused. Regarding the multipath config itself, this is the default config, functionally the same as the one proposed for MSA2012fc by HP. The virtual one is of course bogus... not to be used, just to demonstrate the failure mode. The actual servers will have a dual-port FC HBA with each port going to separate zones on a switch, with itself being connected with 2 cables each to the 2 controllers (4 in total) of the SAN, so there will be 2 paths for each volume. This is required for this SAN in order to have redundancy for controller failure. I just tried this with the physical server, and it still doesn't work as it should. In lvm.conf, blacklisted all the sd* devices and allowed only /dev/disk/by-id. Or should even the id's of the MP volumes be blacklisted, only allowing the one single PV's id? -- 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/1178721 Title: multipathd fails to create mappings when multipath.conf is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+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
[Bug 1178721] Re: multipathd fails to create mappings when multipath.conf is present
Thank you for your help. I wasn't aware of the limitation (incompatibility) caused by co-deploying LVM and multipath, it was my assumption that multipath would be configured to take precedence over LVM for having PVs on multipath block devices, as having it the other way around, as in multiple paths over LVM logical volumes would not make sense. I can assume that this would be a pretty common scenario, as for example, you may have one volume mapped from SAN over FC on which the tools that LVM offers would be valuable. It would seem that a simple check at boot time, checking whether LVM and multipath are co-deployed, starting multipath first, letting it create paths and then adding those found to LVM's filter. I understand however that this is in no way common usage and requires a skillful enough administrator to be aware of the possible scenarios caused. Regarding the multipath config itself, this is the default config, functionally the same as the one proposed for MSA2012fc by HP. The virtual one is of course bogus... not to be used, just to demonstrate the failure mode. The actual servers will have a dual-port FC HBA with each port going to separate zones on a switch, with itself being connected with 2 cables each to the 2 controllers (4 in total) of the SAN, so there will be 2 paths for each volume. This is required for this SAN in order to have redundancy for controller failure. I just tried this with the physical server, and it still doesn't work as it should. In lvm.conf, blacklisted all the sd* devices and allowed only /dev/disk/by-id. Or should even the id's of the MP volumes be blacklisted, only allowing the one single PV's id? -- 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/1178721 Title: multipathd fails to create mappings when multipath.conf is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+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
[Bug 1178721] Re: multipathd fails to create mappings when multipath.conf is present
http://h2.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=encc=ustaskId=115prodSeriesId=3559651prodTypeId=18964objectID=c01476873 This is the config recommended by HP for our SAN (2000 series is down there), mine is functionally the same. There is no way to sense the priorities of the paths for this SAN, wouldn't that mean that if one path were lost, some of the IO would get lost as well, or would the protocol sense that and retry. Just wondering. -- 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/1178721 Title: multipathd fails to create mappings when multipath.conf is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+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
[Bug 1178721] Re: multipathd fails to create mappings when multipath.conf is present
** Attachment added: udev log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+attachment/3672267/+files/udev.multipath-BROKEN -- 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/1178721 Title: multipathd fails to create mappings when multipath.conf is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+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
[Bug 1178721] Re: multipathd fails to create mappings when multipath.conf is present
https://help.ubuntu.com/12.10/serverguide/multipath-devices.html You cannot have a default LVM config co-exist with multipath. They will race to grab the SD device for map creation and whoever gets there first wins; they both use device mapper. LVM is configured using UDEV so it's the first pass, multipath in run by legacy rc script. You must configure LVM to blacklist all SD devices. Then, you must configure LVM to use allow the disks necessary for the root volume using the UDEV names e.g. /dev/disk/by-id SD names are never deterministic, sorry, that's what udev us for. When the multipath volume is not root, you can easily test the config per the documentation. Any time a change is made to either multipath.conf or lvm.conf, the initrd must be updated; also in the documentation. Multipath usually runs last, so if you didn't push the lvm blacklist to the ramdisk, by the time multipath runs there's nothing left for it to attach to. Your virtual multipath is bogus, there's nothing that will arbitrate write ordering, the block names aren't deterministic, and they never can be because they don't have make/model/serial# which udev uses to create unique names. You could easily multipath your root disk + a MP leg and be left with swiss cheese based on scan ordering or hotplug events. If you remove LVM from the stack and follow the directions for properly propagating multipath to the ramdisk, it will work. Start small, then add an additional layer of complexity. There does not exist a tool which integrates the deployment of LVM + multipath anywhere, you have to understand both and configure by hand. It is challenging to deploy an LVM config that co-exits with multipath. Good luck. ** Changed in: multipath-tools (Ubuntu) Status: New = Confirmed -- 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/1178721 Title: multipathd fails to create mappings when multipath.conf is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+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
[Bug 1178721] Re: multipathd fails to create mappings when multipath.conf is present
** Changed in: multipath-tools (Ubuntu) Status: Confirmed = Triaged -- 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/1178721 Title: multipathd fails to create mappings when multipath.conf is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+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
