Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, I am closing it because the bug has been fixed
in the latest development version of Ubuntu - Precise Pangolin. It won't
be fixed in previous versions of Ubuntu because the package doesn't fit
the requiremen
I have the same problem. The workaround provided by Leo is not working
for me, because /dev/mapper/ does not contain the right uuid anymore.
ls /dev/mapper/ -l
total 0
crw-rw 1 root root 10, 59 2010-08-25 14:15 control
The curios thing is, if i look into "Disk Utility" i can see that usb-
d
Workaround:
sudo dmsetup remove /dev/mapper/udisks-luks-uuid-xx
It seems to have been fixed upstream. Source:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554600
** Bug watch added: Debian Bug tracker #554600
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554600
** Also affect
This is more of a feature request than a bug in cryptmount.
As already noted, the original source of the problem seems to be the behaviour
of the LVM system.
--
LVM unusable after uncleanly unplugging USB disk
https://bugs.launchpad.net/bugs/223583
You received this bug notification because you
This bug affects me too.
I marked other packages since they could contain a workaround for this
problem themselves.
Perhaps:
? Let non-root users remove the LVM after checking that the corresponding
physical device is absent.
? Not try to create the /dev/mapper/udisks-luks-uuid-xx when
I believe this is a design defect of the upstream lvm and likely won't
be resolved any time soon. As a workaround, you should be able to
destroy the rogue mappings with dmsetup.
** Changed in: lvm2 (Ubuntu)
Importance: Undecided => Low
** Changed in: lvm2 (Ubuntu)
Status: New => Triage
