cryptsetup: "c_swap_unformatted" still exists after system boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cryptsetup |
Unknown
|
Unknown
|
|||
cryptsetup (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
udev (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: cryptsetup
Using Karmic,
cryptsetup version : 2:1.0.6+
Confirmed after several machines boots : When using random encrypted swap, both "/dev/mapper/
# ll /dev/mapper/c_swap*
brw-rw---- 1 root disk 252, 16 2010-01-03 19:20 /dev/mapper/c_swap
brw-rw---- 1 root disk 252, 16 2010-01-03 19:20 /dev/mapper/
(The same behaviour is NOT observed for encrypted /tmp)
/etc# egrep swap fstab crypttab
fstab:/
crypttab:c_swap /dev/mapper/
tags: | added: patch |
Changed in udev (Ubuntu): | |
status: | New → Invalid |
I have this problem here with Lucid as of today, too.
# ls /dev/mapper/
control home home_unformatted root var var_unformatted
According to the cryptsetup bugreport this could be caused by
udev or DeviceKit-disks.
At the moment I assume that this causes mountall not to mount my
home and var partition which means I have to manually support
every single boot process.