Hi!

I'm trying to get my Dell desktop machine with a SuSE to suspend to disk. This is usually successful once, but after that it's not anymore. First the problem seemed to be that I was low on swap space. (2G swap space, 4G memory in the machine.)

Now I've added 2 swap files, so I have 8G swap in all:
original swap partition 2G
swap file 1 2G
swap file 2 2G

The swap files serve as swap indeed:

# free -m total used free shared buffers cached
Mem: 4048 3796 251 0 41 1985
-/+ buffers/cache: 1770 2278
Swap: 8199 0 8199

However, when I call s2disk, in /var/log/pm-suspend.log I see:

[...]
+ /usr/sbin/s2disk --config /var/lib/s2disk.conf
s2disk: Snapshotting system
s2disk: Not enough free swap
s2disk: retrying, image_size=0
s2disk: Snapshotting system
s2disk: alloc_swap_page failed
s2disk: write_image -> ENOSPC
+ RET=28
+ set +x
[...]


How much more swap does the system need? Or does it have to be one contiguous partition and cannot be split up like I did?


Thanks,
Agoston

I've never seen a split partition in suspending - doesn't mean it can't be done

The usual gotchas are: have you the parameter resume=/dev/sda2 or wherever
The swap partition is hardcoded into the kernel. Have you got the correct value there?

Errm, am I missing something, or is that more like 6G of swap?

Normally, you'd have thought 6G was going to be adequate, and, even 2G has a good chance of being adequate, for normal applications.

You have to find space for all of the application data that you have in ram, plus all of that data that you have in use in swap. I'm not sure in enough detail, but you shouldn't, in principle, need to find space for the 'buffers' or 'cached'. This data may or may not get compressed before getting stored, depending on distro and version.

That suggests that you are starting with something approaching 4G of data, and s2ram is not working. It does suggest that all of your swap space is somehow not not available for suspend. I can only guess whether it would fail with multiple swap partitions or whether it is something to do with swap files that is the problem, but the suggestion seems strong that it is one of those two that is causing the full amount of space not to be usable in this case.

@salasi have a look at the "free -m" output.
Do you have a /etc/suspend.conf ?. What does it say ?.

I did. I was trying to give the OP things to think about for himself, rather than an answer.