[systemd-bugs] [Bug 90656] New: cryptsetup: indefinite wait for encrypted swap device

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=90656

            Bug ID: 90656
           Summary: cryptsetup: indefinite wait for encrypted swap device
           Product: systemd
           Version: unspecified
          Hardware: x86-64 (AMD64)
               URL: http://https://bugs.gentoo.org/show_bug.cgi?id=550358
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: ua_bugzilla_freedesktop at binary-island.eu
        QA Contact: systemd-bugs at lists.freedesktop.org

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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150526/2b041336/attachment.html>