[systemd-devel] Option fail mentioned in systemd.mount(5)

[Ivan Shapovalov]

Hi all,

The systemd.mount(5) man page mentions an inexistent mount option fail in the
following context:

nofail, fail
With nofail this mount will be only wanted, not required, by the
local-fs.target. This means that the boot will continue even if this
mount point is not mounted successfully. Option fail has the opposite
meaning and is the default.

Specifying the option fail in fstab produces following message in the log:

kernel: EXT4-fs (sdc1): Unrecognized mount option fail or missing value

So the man page contradicts actual behavior. Should this statement be removed,
or what?

-- 
Ivan Shapovalov / intelfx /

signature.asc
Description: This is a digitally signed message part.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Option fail mentioned in systemd.mount(5)

[Lennart Poettering]

On Fri, 05.12.14 00:20, Ivan Shapovalov (intelfx...@gmail.com) wrote:

 Hi all,
 
 The systemd.mount(5) man page mentions an inexistent mount option fail in 
 the
 following context:
 
 nofail, fail
 With nofail this mount will be only wanted, not required, by the
 local-fs.target. This means that the boot will continue even if this
 mount point is not mounted successfully. Option fail has the opposite
 meaning and is the default.
 
 Specifying the option fail in fstab produces following message in the log:
 
 kernel: EXT4-fs (sdc1): Unrecognized mount option fail or missing value
 
 So the man page contradicts actual behavior. Should this statement be removed,
 or what?

Indeed, neither util-linux nor actually our own code cares about the
fail option, and it is the default anyway.

I removed this now from the man page.

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel