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

[Ivan Suzdal]

** Description changed:

- When on bare metal uses NVMe devices - kpartx cause kernel oops. 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.
+ 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?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, 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

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