https://bugzilla.novell.com/show_bug.cgi?id=779441 https://bugzilla.novell.com/show_bug.cgi?id=779441#c0 Summary: systemd.mount man page is inaccurate / incomplete Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86 OS/Version: openSUSE 12.2 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: cshorler@googlemail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20100101 Firefox/15.0 I have a filesystem that fails to mount, it's not critical for system operation SysV used to just report it and move on SystemD drops to a emergency console. The manpage for systemd.mount states: If an mount point is beneath another mount point in the file system hierarchy, a dependency between both units is created automatically. On reading the source here: http://cgit.freedesktop.org/systemd/systemd/tree/src/mount.c?id=v44 ~ line 340 and onwards Effective mount options are: x-systemd-mount, x-systemd-automount, nofail etc. (assuming our version is similar - I briefly checked applied patches on the build service package and didn't notice anything significant) * Use of nofail changes the type of the dependency generated by SystemD from Requires to Wants. - The systemd.mount man page doesn't have this information (relevance of nofail) - The man page also states x-systemd.mount (which appears to be incorrect) - The systemd.special man page indicates something else again in the local-fs.target section. Reproducible: Always Steps to Reproduce: 1. Set the hibernation flag on an NTFS partition (then mount won't be able to mount it without additional options). 2. Boot the system system fails to initialise 3. Add x-systemd-mount,nofail to options in fstab. 4. Ctrl-D system boots -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.