[Bug 1386637] Re: multipath shows non-mpath disks as being multipath
Mauricio Faria de Oliveira
mauricfo at linux.vnet.ibm.com
Tue Sep 22 12:20:21 UTC 2015
Hi @mathieu-tl,
Marking as verification-failed since the version from -proposed hits a segfault in 'multipath -l'.
Here are some details/stack trace:
It segfaults:
# multipath -l
Segmentation fault
Trusty / 14.04.3:
# lsb_release -d
Description: Ubuntu 14.04.3 LTS
# uname -a
Linux plzp17 3.19.0-29-generic #31~14.04.1-Ubuntu SMP Thu Sep 10 09:45:11 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
Using multipath-tools from trusty-proposed (0.4.9-3ubuntu7.5)
# apt-cache policy multipath-tools
multipath-tools:
Installed: 0.4.9-3ubuntu7.5
Candidate: 0.4.9-3ubuntu7.5
Version table:
*** 0.4.9-3ubuntu7.5 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main ppc64el Packages
100 /var/lib/dpkg/status
0.4.9-3ubuntu7.4 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main ppc64el Packages
0.4.9-3ubuntu7 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main ppc64el Packages
# dpkg -l | grep 'multipath\|kpartx'
ii kpartx 0.4.9-3ubuntu7.5 ppc64el create device mappings for partitions
ii kpartx-boot 0.4.9-3ubuntu7.5 all Provides kpartx during boot
ii multipath-tools 0.4.9-3ubuntu7.5 ppc64el maintain multipath block device access
ii multipath-tools-boot 0.4.9-3ubuntu7.5 all Support booting from multipath devices
Problem contained in libmultipath, not any external library/component, in the initialization phase:
# gdb multipath
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
...
(gdb) run -l
Starting program: /sbin/multipath -l
...
Program received signal SIGSEGV, Segmentation fault.
0x00003fffb7e3fd70 in vector_alloc_slot () from /lib/libmultipath.so.0
(gdb) bt
#0 0x00003fffb7e3fd70 in vector_alloc_slot () from /lib/libmultipath.so.0
#1 0x00003fffb7e3e200 in keyword_alloc () from /lib/libmultipath.so.0
#2 0x00003fffb7e3e2c4 in install_keyword_root () from /lib/libmultipath.so.0
#3 0x00003fffb7e5ac34 in init_keywords () from /lib/libmultipath.so.0
#4 0x00003fffb7e4a54c in load_config () from /lib/libmultipath.so.0
#5 0x0000000010002bcc in ?? ()
#6 0x00003fffb7c94d00 in generic_start_main (main=0x10002b10, argc=<optimized out>,
argv=0x3ffffffffa28, auxvec=0x3ffffffffb30, init=<optimized out>, rtld_fini=<optimized out>,
stack_end=<optimized out>, fini=<optimized out>) at ../csu/libc-start.c:287
#7 0x00003fffb7c94ef8 in __libc_start_main (argc=<optimized out>, argv=<optimized out>,
ev=<optimized out>, auxvec=<optimized out>, rtld_fini=<optimized out>, stinfo=<optimized out>,
stack_on_entry=<optimized out>) at ../sysdeps/unix/sysv/linux/powerpc/libc-start.c:93
#8 0x0000000000000000 in ?? ()
(gdb)
Downgrading to version in trusty-updates (0.4.9-3ubuntu7.4):
# apt-get install {multipath-tools,kpartx}{,-boot}=0.4.9-3ubuntu7.4
...
The following packages will be DOWNGRADED:
kpartx kpartx-boot multipath-tools multipath-tools-boot
...
Get:1 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main multipath-tools-boot all 0.4.9-3ubuntu7.4 [6,070 B]
Get:2 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main multipath-tools ppc64el 0.4.9-3ubuntu7.4 [108 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main kpartx-boot all 0.4.9-3ubuntu7.4 [2,116 B]
Get:4 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main kpartx ppc64el 0.4.9-3ubuntu7.4 [19.0 kB]
...
Now it works fine:
# multipath -l
36005076303ffd2a40000000000000345 dm-2 AIX,VDASD
size=50G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
|- 0:0:4:0 sdd 8:48 active undef running
`- 1:0:4:0 sdh 8:112 active undef running
36005076303ffd2a40000000000000344 dm-1 AIX,VDASD
size=50G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
|- 0:0:3:0 sdc 8:32 active undef running
`- 1:0:3:0 sdg 8:96 active undef running
36005076303ffd2a40000000000000343 dm-0 AIX,VDASD
size=50G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
|- 0:0:2:0 sdb 8:16 active undef running
`- 1:0:2:0 sdf 8:80 active undef running
# echo $?
0
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1386637
Title:
multipath shows non-mpath disks as being multipath
Status in multipath-tools package in Ubuntu:
Fix Released
Status in multipath-tools source package in Trusty:
Fix Committed
Bug description:
[Impact]
Users of multipath-tools on systems which exhibit both multipathed and non-multipathed drives or some USB devices (some USB devices may still be picked up by multipath-tools if multipath-capable).
[Test case]
- Boot on a system with multipathed disks with the previous version of multipath-tools
- Upgrade to the new version; verify that /etc/multipath/wwids is created and contains all the right device WWIDs, and that 'sudo multipath -ll' has the same devices.
- Reboot and verify that the system still boots correctly.
- [udev] Using Fibre-Channel hardware: verify that multipath still behaves correctly for path degradation scenarios (see below).
After rebooting, you should verify that /proc/mounts correctly lists
the multipath device (/dev/mapper/*), and that /proc/swaps also lists
any swap partitions that should be on a multipathed disk as a
/dev/dm-* device.
PATH DEGRADATION:
-- This test requires fibre-channel hardware or another method to be able to disconnect paths to a drive.
1) verify that on disconnecting a path, it is properly detected as being in degraded mode by multipath-tools; and shows as such in 'multipath -ll'.
2) verify that on reconnection, the path shows up again as ready or OK in 'multipath -ll'.
[Regression potential]
Systems in complex setups mixing both multipathed and non-multipathed disks, or with particularly slow disk controllers may fail to boot or show delays in booting. Systems requiring a particular set of partitions to be available in early boot (past the typical installs on /, some may require /usr to be available for some daemons to load on boot) could fail to properly start up all the software on boot; these should be considered as regressions only if devices do not properly show up in 'sudo multipath -ll' output.
Users seeing issues should preferrably include the output of 'sudo
multipath -v4' to bug reports to help developers in debugging.
Udev rules have been changed in this case, because they interfere with
the proper behavior of multipath 0.4.9 with the patches included as
backported from 0.5.0; this has the potential to strongly impact the
detection of change events on multipath devices; if path degradation
or new device detection fails, this should be considered an important
regression of multipath-tools.
---
Problem Description
======================
non-multpath disks are classified as multipath after the multipath-tools package is installed.
---uname output---
Linux uu04g1 3.16.0-21-generic #28-Ubuntu SMP Mon Oct 6 15:57:32 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Tuleta pKVM guest
Steps to Reproduce
=========================
1) Create a guest with an unused, non-mpath disk (not the install disk) (a qemu img file is fine).
2) apt-get install multipath-tools.
3) multipath -ll.
4) Note that your file backed disks are showing up as mpath disks.
Userspace tool common name: multipath
The userspace tool has the following bit modes: 64
System Dump Info:
The system is not configured to capture a system dump.
Userspace rpm: multipath-tools
Userspace tool obtained from project website: multipath-tools v0.4.9 (05/33, 2016)
== Comment: #1 - Edward R. Cheslek <echeslak at us.ibm.com> - ==
root at uu04g1:~# multipath -ll
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:1:0 sdb 8:16 active ready running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:2:0 sdc 8:32 active ready running
root at uu04g1:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 20G 0 disk
??sda1 8:1 0 7M 0 part
??sda2 8:2 0 19.1G 0 part /
??sda3 8:3 0 896M 0 part [SWAP]
sdb 8:16 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-1-0
252:0 0 20G 0 mpath
sdc 8:32 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-2-0
252:1 0 20G 0 mpath
root at uu04g1:~#
root at uu04g1:~# lsscsi
[0:0:0:0] disk QEMU QEMU HARDDISK 2.0. /dev/sda
[0:0:1:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdb
[0:0:2:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdc
== Comment: #2 - Edward R. Cheslek <echeslak at us.ibm.com> - 2014-10-08 22:27:09 ==
This is the xml file of the affected guest. Please note that all disks are file backed.
root at uu04g1:~# multipath -l
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:1:0 sdb 8:16 active undef running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:2:0 sdc 8:32 active undef running
root at uu04g1:~# multipath -v2
root at uu04g1:~#
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1386637/+subscriptions
More information about the foundations-bugs
mailing list