configure swap

[dyindude]

reference guide for ideas on how to handle this

[dyindude]

should support

• ~another partition for swap (sda5?)~ if we did this, a dead disk means unbootable system, no accessible swap
  • however:

  • The RESUME=none is necessary to disable resuming from hibernation. This does not work, as the zvol is not present (because the pool has not yet been imported) at the time the resume script runs. If it is not disabled, the boot process hangs for 30 seconds waiting for the swap zvol to appear.

  • I wonder if it's possible to defer the resume script until after disks/zfs?
  • something like this?

  • echo RESUME=/dev/mapper/system-swap > /etc/initramfs-tools/conf.d/resume

  • really, just need zfs-initramfs to run before resume, will check this on a run
• swap as zvol
• no swap
• specify size (default to 4-8GB)
• pool placement (root vs data etc)

[dyindude]

actually seem to have gotten hibernate to work by moving /usr/share/initramfs-tools/scripts/local-premount/resume to /usr/share/initramfs-tools/scripts/local-bottom/resume (which allows /usr/share/initramfs-tools/scripts/local-premount/zfs to run before resume, but after cryptroot)

[dyindude]

still a little slowlyness on boot..is this normal when resume is enabled?

[dyindude]

per https://github.com/zfsonlinux/zfs/issues/260 , the greater problem is that the filesystem isn't frozen/thawed as a part of this process, so it's probably better to shelf the idea of enabling hibernate on a zvol until upstream sorts it out

[dyindude]

because of this, I may actually implement an optional swap partition (that can still be mdadm/LUKS), since I will want to be able to use suspend-to-disk on my laptop

[dyindude]

reading over that issue some more, I realize that this is a problem for suspend/resume regardless of where the swap is located, so I'm going to follow the guide and set RESUME=none when setting up swap