[systemd-bugs] [Bug 86062] New: x-systemd.device-timeout=0s causes halts boot in endless wait due to 's' suffix

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 86062
           Summary: x-systemd.device-timeout=0s causes halts boot in
                    endless wait due to 's' suffix
           Product: systemd
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: ce0c5679c447a438 at spamherelots.com
        QA Contact: systemd-bugs at lists.freedesktop.org

The short: an fstab entry specifing "0s", note the 's' suffix makes the systemd
startup wait indefinitely, and I was unable to get to rescue/maintenane mode
without booting through a USB stick and manually mounting/editing fstab.

systemd: 217 (systemctl -version)
kernel: 3.17.2-300.fc21.x86_64

fstab entry:
/dev/fedora/storage1 /mnt/storage  ext4  defaults,x-systemd.device-timeout=0s 1
2

What's wrong with that?
- systemd.mount(5) suggests '0s' is acceptable. 
- it's also unclear if 0 means unbounded delay or no delay allowed.
- it bricks the system, rescue prompt is unreachable, requires boot from usb
stick to fix.

extra info:
The startup sequence spits out a spurious "You're in maintenance mode..."
dracut prompt I couldn't interact with, but the systemd process continues for a
few steps until it hangs shortly after with:
"A start job is running for dev-mapper-storage1... (time / ETA)"

-- 
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/20141109/c72ff544/attachment.html>