This bug was fixed in the package cryptsetup - 2:1.4.1-2ubuntu4
---------------
cryptsetup (2:1.4.1-2ubuntu4) precise; urgency=low
* Our swap creation can trigger udev change events, which means udev may be
holding the device open at the time we try to call 'dmsetup rename' and
cause the /subsequent/ events to be missed because of dmsetup creating
device nodes by hand. So call 'udevadm settle' before 'dmsetup rename',
to ensure blkid is out of the way first. This should ensure swap
partitions are found by mountall in a non-racy manner. LP: #874774.
-- Steve Langasek <[email protected]> Fri, 13 Apr 2012 20:23:21 -0700
** Changed in: cryptsetup (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/874774
Title:
could not mount /dev/mapper/cryptswap1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/874774/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
