/proc/swaps:
----
Filename Type Size Used Priority
/dev/mapper/hidalgo-swap_1 partition 1048568 117996 -1
----
Encrypted swap is especially useful when using hibernation (because there's no point in having disk encryption at all if you don't encrypt the swap when hibernating). Maybe in the case of swap recreated at each boot it would make sense, but in my case, the setup is:
/dev/sda5 is encrypted to /dev/mapper/sda5_crypt (using dm-crypt and luks)
/dev/mapper/sda5_crypt has a LVM volume group hidalgo
hidalgo VG has multiple LV: root, home and swap_1, swap_1 being used as swap.
In my case, encryption key is provided at boot/resume time and everything works fine.
I'm not 100% sure my problem comes from encryption, but if it does, I think it'd make sense to allow it.
Hi,
it seems that the current behavior will break hibernation on my laptop.
I first reported the bug on debian at http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 555712
Basically, devkit-power doesn't think it could hibernate my laptop, while pm-hibernate works pretty fine (and echo disk > /sys/power/state too).
It seems it could be related to me using full disk encryption with luks.
Some info:
/etc/fstab: hidalgo- root / ext3 errors= remount- ro,relatime, commit= 30 0 1 hidalgo- home /home ext3 defaults, relatime, commit= 30 0 2 hidalgo- swap_1 none swap sw 0 0
----
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mapper/
/dev/sda1 /boot ext3 defaults,relatime 0 2
/dev/mapper/
/dev/mapper/
/dev/cdrom1 /media/cdrom0 udf,iso9660 user,noauto 0 0
----
/etc/crypttab:
----
sda5_crypt /dev/sda5 none luks
----
/proc/swaps: hidalgo- swap_1 partition 1048568 117996 -1
----
Filename Type Size Used Priority
/dev/mapper/
----
Encrypted swap is especially useful when using hibernation (because there's no point in having disk encryption at all if you don't encrypt the swap when hibernating). Maybe in the case of swap recreated at each boot it would make sense, but in my case, the setup is:
/dev/sda5 is encrypted to /dev/mapper/ sda5_crypt (using dm-crypt and luks) sda5_crypt has a LVM volume group hidalgo
/dev/mapper/
hidalgo VG has multiple LV: root, home and swap_1, swap_1 being used as swap.
In my case, encryption key is provided at boot/resume time and everything works fine.
I'm not 100% sure my problem comes from encryption, but if it does, I think it'd make sense to allow it.
Cheers,
--
Yves-Alexis