[Lucid] [Regression] crypsetup leaves temporary-cryptsetup-nnnn files lying around in /dev/mapper/
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cryptsetup (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: cryptsetup
Looks like a bug that existed looooong ago (2007/11, bug #162582 ) and that had been fixed loooooong ago has reappeared in Lucid since a couple weeks (hint : latest updates...)
Same description as in the far away past : « In some situations (I could not yet clearly determine in which exact conditions this happens (*) ), after running cryptsetup, a device /dev/mapper/
(*) "cryptsetup luksOpen" is a good candidate for ending with temp things lying around.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: cryptsetup 2:1.1.0~
ProcVersionSign
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Fri May 14 13:01:24 2010
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: cryptsetup
crypttab:
# <target name> <source device> <key file> <options>
c_VG1 /dev/sda6 UUID=524d4883-
#c_VG1 /dev/sda6 none luks,tries=3
Just to verify that internal cryptsetup "defense" against broken udev rules work at least:
Can you post here output of "dmsetup table" of that orphaned temportary- cryptsetup- * device?
(It should be already replaced by error segment to prevent keyslot access.)