[Bug 1551828] Re: kpartx causes kernel oops when NVMe devices is not in blacklist

[Launchpad Bug Tracker]

This bug was fixed in the package multipath-tools - 0.5.0-7ubuntu16

---------------
multipath-tools (0.5.0-7ubuntu16) xenial; urgency=medium

  * debian/patches/dm-multipath-backlist-nvme-5c412e47.patch: blacklist NVMe
    from multipath, otherwise kpartx calls will hang. This is because mpath
    works at the request level (which NVMe bypasses), so multipathing is not
    supported on NVMe. (LP: #1551828)

 -- Mathieu Trudel-Lapierre <mathieu-tl at ubuntu.com>  Tue, 01 Mar 2016
11:55:13 -0500

** Changed in: multipath-tools (Ubuntu)
       Status: In Progress => Fix Released

-- 
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/1551828

Title:
  kpartx causes kernel oops when NVMe devices is not in blacklist

Status in multipath-tools package in Ubuntu:
  Fix Released
Status in multipath-tools source package in Trusty:
  Triaged

Bug description:
  When on bare metal uses NVMe devices - kpartx cause kernel oops.
  http://paste.openstack.org/show/488638/

  Also any tools which works with disks (e.g. fdisk, lsblk) hangs in D state (uninterruptible sleep) while trying to to read /dev/dm-X.
  This bug is already described and fixed in upstream (http://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=commitdiff;h=5c412e47e589b5325ed7de6cba86d906a671d9df)

  I made patches for trusty and xenial versions of multipath-tools.
  Patches which fix issue is in attach.
  Could you apply this patches please, at least for trusty version?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551828/+subscriptions