uswsusp oddity
I just tried uswsusp 0.2 and there is a strange problem (2.6.17.8, x86_64):
The swap device used for suspend must be the first swap device, otherwise suspend fails.
Contents of /etc/suspend.conf:
snapshot device = /dev/snapshot
resume device = /dev/hda2
#image size = 350000000
suspend loglevel = 7
#compute checksum = y
#compress = y
#encrypt = y
early writeout = y
#splash = y
Output of /proc/swaps of the failing suspend:
Filename Type Size Used Priority /dev/mapper/swap1 partition 1959920 0 2 /dev/mapper/swap2 partition 1959888 0 3 /dev/hda2 partition 1959920 0 1
Relevant portion of strace of suspend utility:
mlockall(MCL_CURRENT|MCL_FUTURE) = 0stat("/dev/hda2", {st_mode=S_IFBLK|0660, st_rdev=makedev(3, 2), ...}) = 0open("/dev/hda2", O_RDWR) = 3stat("/dev/snapshot", {st_mode=S_IFCHR|0600, st_rdev=makedev(10, 231), ...}) = 0open("/dev/snapshot", O_RDONLY) = 4ioctl(4, 0x4004330a, 0x302) = -1 ENODEV (No such device)
write(2, "suspend: Could not use the resum"..., 57suspend: Could not use the res
ume device (try swapon -a)
There seems to be something wrong with the SNAPSHOT_SET_SWAP_FILE ioctl.
If I do the following sequence suspend works:
swapoff -a
swapon -p 1 /dev/hda2
swapon -a
Signature · 1 line
Andreas Steinmetz SPAMmers use [email protected]
Quoted 4 lines · Andreas Steinmetz
I just tried uswsusp 0.2 and there is a strange problem (2.6.17.8,
x86_64):The swap device used for suspend must be the first swap device, otherwise suspend fails.
This is a known issue, happens also in swsusp. It should be fixed in 2.6.18.
Greetings,
Rafael
Signature · 2 lines
You never change things by fighting the existing reality. R. Buckminster Fuller