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)
Verified; this works as expected:
kpartx -av adds a loop device node and mounts the image, and sets up the
partitions.
kpartx -dv deletes the partition maps and removed the loop device node.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug
Hello Steve, or anyone else affected,
Accepted multipath-tools into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/multipath-
tools/0.4.9-3ubuntu7.9 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Also affects: multipath-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: multipath-tools (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
This bug was fixed in the package multipath-tools - 0.5.0-7ubuntu14
---
multipath-tools (0.5.0-7ubuntu14) xenial; urgency=medium
* debian/patches/kpartx_more_loopback_fixes.patch: fix loopback mounted
files some more: since we stat() the loopback device node, we can't rely
Ugh, yeah, I see now that the patch fixing dealing with loopbacks at all
"regresses" in a way, but not dealing correctly with the loop entries
even though it appears to deal with the devmapper table just fine.
I'm looking at it right now, it's not pretty. There are basically two
ways I can think
** Changed in: multipath-tools (Ubuntu)
Status: New => In Progress
--
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/1543430
Title:
kpartx 0.5.0-7ubuntu11 fails to
Well, it's a problem on s390x, where they are not dedicated VMs.
wgrant has run a cleanup of loopsetup devices now, on those builders.
adding a check to test that losetup -f matches after a kpartx -a / -d
round trip.
--
You received this bug notification because you are a member of Ubuntu
