Bug 90656

Summary:	cryptsetup: indefinite wait for encrypted swap device
Product:	systemd	Reporter:	Matthias Dahl <ua_bugzilla_freedesktop>
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED FIXED	QA Contact:	systemd-bugs
Severity:	normal
Priority:	medium	CC:	evangelos, poncho
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
URL:	https://bugs.gentoo.org/show_bug.cgi?id=550358
Whiteboard:
i915 platform:		i915 features:

Description Matthias Dahl 2015-05-26 08:48:15 UTC

Updating to systemd 220 today (from 219) on a Gentoo system (~amd64), broke the encrypted swap setup I had been using for ages now. Nothing else was touched, except for the systemd upgrade.

The device is properly brought up and listed in /dev/mapper/ but dev-mapper-crypt-swap.device stills waits indefinitely for the device to show up, thus hanging the boot process if swap is listed in fstab.

This is definitely a regression in systemd -- and thus far, I have been unable to figure out what is exactly causing it. :(

crypttab:
crypt-swap /dev/disk/by-id/md-uuid-f4f3dfc8:812e35f6:bfe78010:bc810f04 /dev/urandom swap,cipher=aes-cbc-essiv:sha256,size=256,hash=sha512,x-systemd.device-timeout=15s

One more thing, maybe of relevance: I use dracut for the initrd... but have been doing so for ages as well and I don't see how this could be relevant in this case.

If there is anything I can do to help further debug/diagnose this, please let me know and I will gladly do so.

Comment 1 Matthias Dahl 2015-05-27 07:20:50 UTC

This was caused by:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=6d1b1e0bc6bd020218afc5f05286bf372be283d5

And fixed by:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=185abfc3d6b4e8f804a3f7216cd8b0459593af87

Unfortunately I didn't initially notice that Gentoo's v220 wasn't vanilla but contained a few patches from master. Sorry for that.

Closing as resolved fixed.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.