** Changed in: util-linux (Ubuntu Bionic)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784347
Title:
ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting
partitions name for the mpath
Status in The Ubuntu-power-systems project:
Fix Committed
Status in util-linux package in Ubuntu:
Fix Released
Status in util-linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
Any user of Ubuntu on multipath, where the default path separator has been
changed to something else. This possibly affects other scenarios where the
partition separator can be changed.
[Test case]
1) Install Ubuntu on multipath system
2) Change /etc/multipath.conf to set "path_separator" to "" or "p".
3) Reboot
4) Run 'sudo fdisk -l /dev/mapper/mpathX', to display a device's partitions
where the path separator would be visible.
[Regression potential]
Minimal. This only affects display. Default separator on Ubuntu remains
"-part". If the separator is not one of "", "p", or "-part", then "-part" would
be used, as is already the case.
== Comment: #0 - Chanh H. Nguyen <chngu...@us.ibm.com> - 2018-01-09 11:14:07
==
We have the Ubuntu1804 installed on our BostonLC system. Create a SAN via the
Emulex adapter to have the mpath disk.
Running the fdisk -l and ls -l showing the conflict name for the mpath.
:~# uname -a
Linux boslcp4 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017
ppc64le ppc64le ppc64le GNU/Linux
root@boslcp4:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
:~# fdisk -l /dev/mapper/mpatha
Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 32768 bytes / 32768 bytes
Disklabel type: dos
Disk identifier: 0xa5be904b
Device Boot Start End Sectors Size Id Type
/dev/mapper/mpatha-part1 2048 419432447 419430400 200G 83 Linux
/dev/mapper/mpatha-part2 419432448 838862847 419430400 200G 83 Linux
/dev/mapper/mpatha-part3 838862848 1258291199 419428352 200G 83 Linux
:~# ls -l /dev/mapper/mpatha*
lrwxrwxrwx 1 root root 7 Jan 9 04:04 /dev/mapper/mpatha -> ../dm-0
lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha1 -> ../dm-1
lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha2 -> ../dm-2
lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha3 -> ../dm-3
== Comment: #2 - Chanh H. Nguyen <chngu...@us.ibm.com> - 2018-01-09 11:35:04
==
I just modify the partitions and it is still showing the conflicting name on
partitions.
:~# ls -l /dev/mapper/mpatha*
lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha -> ../dm-0
lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha1 -> ../dm-1
lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha2 -> ../dm-2
lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha3 -> ../dm-3
lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha4 -> ../dm-4
lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha5 -> ../dm-5
lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha6 -> ../dm-6
lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha7 -> ../dm-7
lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha8 -> ../dm-8
:~# fdisk -l /dev/mapper/mpatha
Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 32768 bytes / 32768 bytes
Disklabel type: dos
Disk identifier: 0xa5be904b
Device Boot Start End Sectors Size Id Type
/dev/mapper/mpatha-part1 2048 419432447 419430400 200G 83 Linux
/dev/mapper/mpatha-part2 419432448 838862847 419430400 200G 83 Linux
/dev/mapper/mpatha-part3 838862848 964691967 125829120 60G 83 Linux
/dev/mapper/mpatha-part4 964691968 1258291199 293599232 140G 5
Extended
/dev/mapper/mpatha-part5 964694016 1006637055 41943040 20G 83 Linux
/dev/mapper/mpatha-part6 1006639104 1048582143 41943040 20G 83 Linux
/dev/mapper/mpatha-part7 1048584192 1090527231 41943040 20G 83 Linux
/dev/mapper/mpatha-part8 1090529280 1132472319 41943040 20G 83 Linux
== Comment: #5 - Kyle Mahlkuch <kyle.mahlk...@ibm.com> - 2018-06-26 13:50:12
==
I have created and submitted a patch that should help with this bug. I will
update when/if the patch is accepted.
== Comment: #9 - Kyle Mahlkuch <kyle.mahlk...@ibm.com> - 2018-07-27 09:10:44
==
Here is the patch:
https://github.com/karelzak/util-linux/commit/73775189767195f1d9f5b6b6f6a54e51f61c4356
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1784347/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
