------- Comment From mauri...@br.ibm.com 2015-07-22 22:09 EDT------- Just to sum up with what has already been said.
parted creates the 'p1' block device, via libparted (see dm_add_partition() in arch/linux.c, IIRC) kpartx creates the '-part1' block device (see /lib/udev/rules.d/*-kpartx.rules). In order to test that the '-part1' block device won't show up, you can disable the kpartx.rules file temporarily. Something like this: $ sudo mv /lib/udev/rules.d/*-kpartx.rules /lib/udev/rules.d/*-kpartx.rules.disabled $ sudo udevadm control --reload Another thought. Not sure why latest parted doesn't show this problem (2 block devices for partition #1) If only 'p1' is created, it seems the kpartx udev rules either fail or are not run. If only '-part1' is created, it seems parted didn't create the partition in the devmap. -- 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/1473903 Title: parted will generate two devices when adding one partition on mpath device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1473903/+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
