Unfortunately I still occasionally get the temporary-cryptsetup mapping
left around (as shown by sudo dmsetup ls), though this is much less
frequent now.  I'm afraid that race conditions are probably endemic due
to the design of udev; the way it forks processes into the background it
seems like there is no guarantee that create/remove events will be
handled in the right order.  I wish I knew why this all worked (for me)
under Gutsy.

-- 
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to