Bug#412210: [Pkg-cryptsetup-devel] Bug#412210: cryptsetup: fails to
handle suspend filesystem in swap
Leonard Norrgard
vinsci at refactor.fi
Wed Feb 28 15:41:35 CET 2007
> What does "/lib/udev/vol_id <swappartition>" identify the encrypted and
> unencrypted swap partitions as?
# /lib/udev/vol_id /dev/mapper/VG00-swap
ID_FS_USAGE=crypto
ID_FS_TYPE=crypto_LUKS
ID_FS_VERSION=
ID_FS_UUID= [<an uuid>]
ID_FS_LABEL=
ID_FS_LABEL_SAFE=
# cryptsetup luksOpen /dev/mapper/VG00-swap VG00-swap_crypt
Enter LUKS passphrase:
key slot 0 unlocked.
Command successful.
# /lib/udev/vol_id /dev/mapper/VG00-swap_crypt
ID_FS_USAGE=other
ID_FS_TYPE=suspend
ID_FS_VERSION=s1suspend
ID_FS_UUID=
ID_FS_LABEL=
ID_FS_LABEL_SAFE=
> What is the contents of /etc/crypttab and /etc/fstab
# /etc/crypttab
VG00-home_crypt /dev/mapper/VG00-home none luks
VG00-root_crypt /dev/mapper/VG00-root none luks
VG00-swap_crypt /dev/mapper/VG00-swap none luks,swap
VG00-var_crypt /dev/mapper/VG00-var none luks
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mapper/VG00-root_crypt / ext3 noatime,errors=remount-ro 0 1
/dev/md0 /boot ext3 noatime 0 2
/dev/mapper/VG00-home_crypt /home ext3 noatime 0 2
/dev/mapper/VG00-var_crypt /var ext3 noatime,nodev,nosuid 0 2
/dev/mapper/VG00-swap_crypt none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/scd0 /media/floppy0 auto rw,user,noauto 0 0
debugfs /sys/kernel/debug debugfs defaults,user 0 0
> Which technique does kpowersave use to suspend? (suspend, suspend2, uswsusp?)
That, I don't know - I could maybe look this up later from the source
(it's in the kpowersave package in Debian), or through its project page at
http://sourceforge.net/projects/powersave/
Perhaps the severity of this issue should be raised, as the "normal"
user will not be able to restore data that's only stored in the
suspend filesystem - potential dataloss.
-- Leonard
More information about the Pkg-cryptsetup-devel
mailing list