[systemd-bugs] [Bug 82733] Duplicate target entry in /etc/fstab renders system unbootable

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Aug 18 10:36:24 PDT 2014


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

Lennart Poettering <lennart at poettering.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #1 from Lennart Poettering <lennart at poettering.net> ---
We don't support multiple entries for the same mount point in /etc/fstab. This
used to somewhat work on classic "mount -a", but it actually is not only
incompatible with systemd, but with many other software that parses /etc/fstab,
too.

Moreover, the scheme you describe cannot really work either, since on modern hw
there's usually no time known at which devices have to have shown up.
Especially on USB devices can take any time they like to initialize (this fact
is used on android for example, which only show up on USB after the user got
asked interactively on the device for confirmation). Now if you list both
devices in your fstab, then the this tells the system to wait for the devices
to show up, which means you#d have to plug in both, and otherwise would have to
endure a lengthy timeout. Or you turn off the timeout by adding "nofail" to he
options, but in that case it might happen that neither shows up and is mounted
at boot.

My suggestion to do this properly is by only having one line for the device in
/etc/fstab, and reference the devices by a single /dev/disk/by-label/ link or
suchlike, and use the same label on both devices. That way it doesnt matter
which one is plugged in, the one that's plugged in will be waited for and be
mounted.

Sorry, if this change tripped you up, but the old scheme really only worked out
of luck, and is not supported this way in systemd. Sorry.

-- 
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/20140818/8cd877c7/attachment.html>


More information about the systemd-bugs mailing list