The systemd package has taken over the handling of /etc/crypttab at boot
from cryptsetup (without much coordination AFAICS), and it sounds like
its interpretation of the crypttab is buggy.
"swap" is not synonymous with "random", and should not result in the
device being clobbered, which is what is happening here. In particular,
encrypted persistent swap needs to be supportable for users who wish to
use this for suspend to disk, and this requires a LUKS header (with
UUID).
Note however that for this use case, you *also* don't actually want to
use 'swap' as an option in /etc/crypttab, because this is defined as
"Run mkswap on the created device", and there's no need to do that if
you have a persistent crypted swap.
** Package changed: cryptsetup (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506139
Title:
15.10beta crashes encrypted swap partition
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1506139/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
