Since filing the original report, I've migrated to Debian 6.0 Squeeze; in that environment, dmsetup is successfully run from /lib/cryptsetup/cryptdisks.functions *without* the above patch, that is, cryptsetup works by default.
Note that the patch (see comment #1) simply adds a short delay to /lib/cryptsetup/cryptdisks.functions. Therefore, I do not know whether the bug has been fixed (or was ever present) on Debian 6.0 or whether the bug is merely masked by a change in the timing of startup events, in which case the bug may possibly reappear. Working system (for me) is running the following versions: $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 6.0 (squeeze) Release: 6.0 Codename: squeeze $ uname -a Linux powerbox 2.6.32-5-amd64 #1 SMP Wed Jan 12 03:40:32 UTC 2011 x86_64 GNU/Linux $ dmsetup --version Library version: 1.02.48 (2010-05-20) Driver version: 4.15.0 $ lvm version LVM version: 2.02.66(2) (2010-05-20) Library version: 1.02.48 (2010-05-20) Driver version: 4.15.0 $ cryptsetup --version cryptsetup 1.1.3 $ udevd --version 164 If the bug is still present on Ubuntu, the Debian configuration may offer some clues for resolving it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/612310 Title: dmsetup rename sometimes creates new device name but does not remove original device name -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
