[systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

[Sergei Franco]

Hi,

I am looking at correct way to disable the "feature" of emergency mode when
systemd encounters missing block device entires in fstab.

For example:

the following entry is in /etc/fstab:
UUID=d4a23034-8cbe-44b3-92a5-3d38e1816eff /data               xfs
defaults        0       0

If the drive (d4a23034-8cbe-44b3-92a5-3d38e1816eff) has been detached and
machine rebooted it stops booting with Emergency mode, even though the
/data is not crucial for boot.

In past (eg. with upstart) it would simply generate a warning and continue
to boot.

The emergency mode assumes console access, which requires physical access,
which is quiet difficult if the machine is remote.

I believe the boot should be best effort, give warning and continue to
boot, giving at least partial working system.

Actually further thinking about it, this behaviour is bad even for desktop
scenario.

The correct behaviour should be following: drop in emergency mode only when
crucial to boot files are not available otherwise warn about missing drives
and continue to boot.

Regards.

Sergei.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20160926/6efd5d61/attachment.html>