[Bug 1543430] Re: kpartx 0.5.0-7ubuntu11 fails to remove loop mapping on kpartx -d

[Launchpad Bug Tracker]

This bug was fixed in the package multipath-tools - 0.4.9-3ubuntu7.9

---------------
multipath-tools (0.4.9-3ubuntu7.9) trusty; urgency=medium

  * debian/patches/kpartx-support-device-names-with-spaces.patch: fix loopback
    files unmapping. (LP: #1543430)

multipath-tools (0.4.9-3ubuntu7.8) trusty; urgency=medium

  * debian/patches/kpartx-support-device-names-with-spaces.patch: deal with
    spaces in device names in kpartx too (LP: #1432062)
  * debian/initramfs/local-premount: wait for udev to settle before mounting
    so the by-uuid/ symlinks have a chance to be updated by udev rules.
    (LP: #1503286)
  * Allow device detection all through the initramfs: run multipathd instead
    of only scanning once for devices, so those that come up slower can still
    be used as a root device (LP: #1526984):
    - debian/patches/0050-readonly-bindings_prefix.patch,
      debian/patches/0051-readonly-bindings_multipath.patch,
      debian/patches/0052-readonly-bindings_multipathd.patch,
      debian/patches/0053-readonly-bindings_multipathd_prod.patch: support -B
      to allow multipathd to handle cases where the bindings file is read-only.
    - debian/initramfs/hooks: install multipathd and required directories.
    - debian/initramfs/local-premount: also reload all maps to make sure
      they're ready before we mount.
    - debian/initramfs/local-top: run multipathd rather than a one-off call to
      multipath so that new paths can be correctly added as detected while
      we're still in the initramfs.
    - debian/initramfs/local-bottom: remember to stop multipathd.
    - debian/initramfs/local-bottom, debian/rules: install local-bottom for
      initramfs.
  * debian/patches/lp1496210_add_IBM_XIV_defaults.patch: add support (default
    config values) for the IBM 2810XIV storage system. (LP: #1496210)
  * debian/patches/0054-kpartx-update-option.patch: run kpartx -u rather than
    kpartx -a, so as to remove old partition entries if the partition table
    has changed. (LP: #1473903)
  * debian/patches/multipath_enable_sync_support_1b8082c8.patch,
    debian/patches/kpartx_rely_on_udev_dev_creation_9a632fff.patch: synchronize
    udev, device-mapper and multipath, and let udev deal with creating device
    nodes and symlinks. (LP: #1486370)
  * debian/initramfs/local-top: drop scsi_wait_scan stanza, that module is no
    longer available. (LP: #1538775)

 -- Mathieu Trudel-Lapierre <mathieu-tl at ubuntu.com>  Tue, 09 Feb 2016
16:03:10 -0500

** Changed in: multipath-tools (Ubuntu Trusty)
       Status: Fix Committed => 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/1543430

Title:
  kpartx 0.5.0-7ubuntu11 fails to remove loop mapping on kpartx -d

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

Bug description:
  I've observed in livefs build logs that with kpartx 0.5.0-7ubuntu12,
  'kpartx -d' is not removing the loop mapping (losetup -d).  E.g.,
  build log diff:

   + kpartx -v -d binary/boot/disk.ext4
   del devmap : loop0p1
  -loop deleted : /dev/loop0

  This doesn't seem to be causing any immediate practical problems
  because each livefs build gets a dedicated VM which is torn down
  afterwards, so the mappings do not persist.  But it's definitely
  incorrect for these mappings to persist.

  The good build log used kpartx 0.5.0-7ubuntu9.  Testing the
  intermediate versions, 0.5.0-7ubuntu11 shows the same buggy behavior
  as 12.  10 clears the loop mapping, but also appears to fail to
  correctly set up partitions in my test case so I'm not sure if this
  bug is present or not in 0.5.0-7ubuntu10.

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