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

Andrei Borzenkov arvidjaar at gmail.com
Mon Sep 26 09:38:53 UTC 2016


On Mon, Sep 26, 2016 at 12:27 PM, Oliver Neukum <oneukum at suse.com> wrote:
> On Sun, 2016-09-25 at 23:57 +0200, Reindl Harald wrote:
>>
>> Am 25.09.2016 um 23:52 schrieb Sergei Franco:
>> > 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
>>
>> RTFM - when you don't say "nofail" it's ecpected to be crucial
>>
>> your entry says it's crucial
>
> That in turn raises the question why the default should be different
> than what is used in earlier systems.
>

How it is different? SLES11 would not boot if SAN device mentioned in
/etc/fstab is not present.


More information about the systemd-devel mailing list