lsblk does not use extended WWNs and may return the same ID for two different disks

Bug #1639744 reported by Maik Zumstrull
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
util-linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

lsblk from util-linux in xenial is affected by this bug:
https://github.com/karelzak/util-linux/issues/321

This means that lsblk may return the same identifier for different devices, because it always uses the short WWN, while some devices are only identified uniquely by the full (extended) WWN.

This has been fixed in upstream util-linux for a while, but the version in xenial is just a tick too old. Since the patch is less than 10 lines, maybe you would consider a backport?

To my knowledge, this affects mainly "Enterprise" hardware - logical volumes on fully hardware-driven RAID controllers like HP, Dell, LSI/Avago, and logical volumes on external storage arrays addressed over iSCSI or FC.

Revision history for this message
Dennis Kuhn (d.kuhn) wrote :

Any news on this issue?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in util-linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Steffen Neubauer (sneubauer) wrote :

would like to see a backport of https://github.com/karelzak/util-linux/commit/3b94a098b04c581be353e71a212a6964b53dd640 for xenial as well, is there a way to help?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.