Dan, the workaround seems safe and fix a real issue than some users are
hitting, maybe it would make sense to distro patch include it?
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1838329
Title:
Cryptswap periodically fails to mount at boot due to missing a udev
notification
Status in systemd:
New
Status in systemd package in Ubuntu:
Triaged
Bug description:
On some systems, cryptsetup-based encrypted swap partitions cause
systemd to get stuck at boot. This is a timing-sensitive Heisenbug, so
the rate of occurrence varies from one system to another. Some
hardware will not experience the issue at all, others will only
occasionally experience the issue, and then there are the unlucky who
are unable to boot at all, no matter how many times they restart.
The workaround is for the cryptsetup-generator to generate cryptswap
service entries that call `udevadm trigger` after `mkswap`. This will
ensure that the udev event is triggered, so that systemd is notified
that the encrypt swap partition is ready to activate. This patch has
already been submitted upstream to systemd, but it was not accepted
because it is a workaround for the side effect of systemd not seeing
the udev event upon creating the swap partition.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1838329/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
