Description of problem: kpartx has logic for when to use disk/partition delimiter of 'p'. It's based on whether the disk's name ends with a digit (use 'p') or not (no delimiter). This is behavior relied on by other tools such as parted. When invoked from udev rules, argv always includes a device node of the form "/dev/dm-X" where X is a digit. As a result, kpartx ends up always using a delimiter when invoked from udev rules. It should look up the map name that corresponds to the dm device and base the delimiter decision on that instead. Version-Release number of selected component (if applicable): Whatever's in f19 as of now. How reproducible: Always Steps to Reproduce: 1. Start up a system with multipath and multipathd 2. Observe the names in /dev/mapper for the partitions on that mpath 3. Actual results: Even if the disk is named 'mpatha' the first partition will be named 'mpathap1'. Expected results: The first partition on 'mpatha' should be 'mpatha1'. Additional info:
Proposing as a FinalBlocker: The installer must be able to complete an installation using any network-attached storage devices (e.g. iSCSI, FCoE, Fibre Channel)
Could someone from the LVM team please take a look at this? This will surely be a blocking issue for RHEL-7, so getting this fixed for Fedora 19 will make testing it and ensuring it works in RHEL-7 much easier. Thanks & regards, Phil
This has been fixed. kpartx will now use the basename of the device it is creating to determine the delimiter instead of the device name is was called with.
device-mapper-multipath-0.4.9-50.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/device-mapper-multipath-0.4.9-50.fc19
Thanks for the quick turnaround, Ben.
Package device-mapper-multipath-0.4.9-50.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing device-mapper-multipath-0.4.9-50.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-7197/device-mapper-multipath-0.4.9-50.fc19 then log in and leave karma (feedback).
*** Bug 963625 has been marked as a duplicate of this bug. ***
Switching to a Beta blocker proposal: dlehman says this breaks dmraid, and Beta criteria say: https://fedoraproject.org/wiki/Fedora_19_Beta_Release_Criteria#Hardware_and_firmware_RAID The installer must be able to detect and install to hardware or firmware RAID storage devices.
<dlehman> that will prevent any install to dmraid or mpath AIUI
+1 for beta inclusion
+1 blocker as it breaks dmraid
3 +1s, setting accepted.
device-mapper-multipath-0.4.9-51.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/device-mapper-multipath-0.4.9-51.fc19
device-mapper-multipath-0.4.9-50.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
device-mapper-multipath-0.4.9-51.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 962831 has been marked as a duplicate of this bug. ***