[Bug 1711749] Comment bridged from LTC Bugzilla
bugproxy
bugproxy at us.ibm.com
Mon Sep 4 12:29:20 UTC 2017
------- Comment From rosattig at br.ibm.com 2017-09-04 08:19 EDT-------
Hello, here's the problem description that was pointed in another bug in our downstream bug tracker (ibm.com):
---Problem Description---
NVMe disks are detected as multipath disks.
They are NVMe namespaces from a single subsystem / controller.
[anaconda root at ltciofvtr-spoon1 ~]# lsmod nvme
Usage: lsmod
[anaconda root at ltciofvtr-spoon1 ~]# lsmod | grep nvme
nvmem_core 21408 1 at24
nvme 32482 64
nvme_core 53962 33 nvme
[anaconda root at ltciofvtr-spoon1 ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n8 259:8 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n26 259:26 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n16 259:16 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
loop1 7:1 0 2G 1 loop
??live-base 253:1 0 2G 1 dm
??live-rw 253:0 0 2G 0 dm /
nvme0n6 259:6 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n24 259:24 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n14 259:14 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n32 259:32 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
sdb 8:16 1 931.5G 0 disk
??sdb2 8:18 1 1G 0 part
??sdb3 8:19 1 930.5G 0 part
? ??rhelaa_ltciofvtr--spoon1-root 253:6 0 50G 0 lvm
? ??rhelaa_ltciofvtr--spoon1-home 253:4 0 876.5G 0 lvm
? ??rhelaa_ltciofvtr--spoon1-swap 253:5 0 4G 0 lvm
??sdb1 8:17 1 4M 0 part
nvme0n4 259:4 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n22 259:22 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n12 259:12 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n30 259:30 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n2 259:2 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n20 259:20 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n10 259:10 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n29 259:29 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n19 259:19 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n9 259:9 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n27 259:27 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n17 259:17 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
loop2 7:2 0 512M 0 loop
??live-rw 253:0 0 2G 0 dm /
nvme0n7 259:7 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n25 259:25 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
nvme0n15 259:15 0 28G 0 disk
??mpatha 253:2 0 28G 0 mpath
??mpatha1 253:3 0 28G 0 part
loop0 7:0 0 325.8M 1 loop
??mpatha1 253:3 0 28G 0 part
sda 8:0 1 931.5G 0 disk
[terminated]
Machine Type = PowerNV 8335-GTC
---uname output---
4.11.0-16.el7a.ppc64le
-------
Seeing this not just in installer, but also on the OS.
# multipath -ll
mpatha (MZPLL1T6HEHP_S3RVNA0J300260) dm-6 ,
size=28G features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
| `- #:#:#:# nvme0n1 259:0 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n10 259:10 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n11 259:11 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n12 259:12 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n13 259:13 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n14 259:14 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n15 259:15 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n16 259:16 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n17 259:17 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n18 259:18 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n19 259:19 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n2 259:2 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n20 259:20 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n21 259:21 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n22 259:22 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n23 259:23 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n24 259:24 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n25 259:25 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n26 259:26 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n27 259:27 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n28 259:28 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n29 259:29 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n3 259:3 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n30 259:30 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n31 259:31 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n32 259:32 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n4 259:4 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n5 259:5 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n6 259:6 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n7 259:7 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- #:#:#:# nvme0n8 259:8 active ready running
`-+- policy='service-time 0' prio=1 status=enabled
`- #:#:#:# nvme0n9 259:9 active ready running
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n8 259:8 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n26 259:26 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n16 259:16 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n6 259:6 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n24 259:24 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n14 259:14 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n32 259:32 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
sdb 8:16 1 931.5G 0 disk
??sdb2 8:18 1 1G 0 part
??sdb3 8:19 1 930.5G 0 part
? ??rhelaa_ltciofvtr--spoon1-home 253:4 0 876.5G 0 lvm
? ??rhelaa_ltciofvtr--spoon1-root 253:5 0 50G 0 lvm
? ??rhelaa_ltciofvtr--spoon1-swap 253:3 0 4G 0 lvm
??sdb1 8:17 1 4M 0 part
nvme0n4 259:4 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n22 259:22 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n12 259:12 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n30 259:30 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n2 259:2 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n20 259:20 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n10 259:10 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n29 259:29 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n19 259:19 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n9 259:9 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n27 259:27 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n17 259:17 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n7 259:7 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n25 259:25 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n15 259:15 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n5 259:5 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n23 259:23 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n13 259:13 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n31 259:31 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
sda 8:0 1 931.5G 0 disk
??sda2 8:2 1 1G 0 part /boot
??sda3 8:3 1 930.5G 0 part
? ??rhelaa_ltciofvtr--spoon100-swap 253:1 0 4G 0 lvm [SWAP]
? ??rhelaa_ltciofvtr--spoon100-home 253:2 0 876.5G 0 lvm /home
? ??rhelaa_ltciofvtr--spoon100-root 253:0 0 50G 0 lvm /
??sda1 8:1 1 4M 0 part
nvme0n3 259:3 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n21 259:21 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n11 259:11 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n1 259:0 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n28 259:28 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
nvme0n18 259:18 0 28G 0 disk
??mpatha 253:6 0 28G 0 mpath
??mpatha1 253:7 0 28G 0 part
[root at ltciofvtr-spoon1 ~]#
--
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/1711749
Title:
multipath-tools: Backport 2 patches to Ubuntu 17.10 (NVMe disks are
detected as multipath disks)
Status in The Ubuntu-power-systems project:
Incomplete
Status in multipath-tools package in Ubuntu:
Incomplete
Bug description:
== Comment: #0 - Rodrigo R. Rosatti Galvao <rosattig at br.ibm.com> - 2017-08-16 12:51:37 ==
NVMe disks are being detected as multipath disks, as pointed in the BZ 157373. https://bugzilla.linux.ibm.com/show_bug.cgi?id=157373
There are two upstream commits in multipath-tools that solve this
issue:
4dd25783e139 Fill NVMe specific path info
c2db19ced1ec libmultipath: fix over-long NVME WWIDs
In order to solve this issue on Ubuntu, the 2 patches must be
backported to multipath-tools package.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711749/+subscriptions
More information about the foundations-bugs
mailing list