Bug#412210: [Pkg-cryptsetup-devel] Bug#412210: cryptsetup: fails to handle suspend filesystem in swap

[David Härdeman]

On Wed, February 28, 2007 15:41, Leonard Norrgard said:
>> What does "/lib/udev/vol_id <swappartition>" identify the encrypted and
>> unencrypted swap partitions as?

<snip>

>> What is the contents of /etc/crypttab and /etc/fstab

<snip>

Thanks for the files.

Could you provide me with the contents of /conf/conf.d/cryptroot from the
initramfs image?

The easiest way to do this is someting like this:
mkdir ~/tmpdir
cd ~/tmpdir
cp /boot/<initramfsfile> init.gz
gunzip init.gz
cpio -i < init

The file should then be found in ~/tmpdir/conf/conf.d/cryptroot

Also, what behaviour do you get when you boot after the suspend? Does it
try to setup the swap partition but fails? Does it print error messages?
Is the swap partition silently ignored?

What arguments do you use when booting? (cat /proc/cmdline)

>> 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/

Thanks, vol_id has already provided the answer (suspendv1 - aka the
regular in-kernel suspend)

> 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.

Perhaps...but not yet, there are plenty of users (myself included) who
suspend/resume with crypto works for

-- 
David Härdeman