Re: Antw: failing unmounts during reboot

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Mo, 29.07.19 08:23, Ulrich Windl (Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx) wrote:

> >>> Frank Steiner <fsteiner-mail1@xxxxxxxxxxxxxx> schrieb am 25.07.2019 um 14:14 in
> Nachricht <913a3c04-a666-b44b-c6ec-fe3d8a7fe95e@xxxxxxxxxxxxxx>:
> > Ulrich Windl wrote:
> >
> >> *1: I have a support call open with SUSE:
> >> Before systemd (almost) all processes were killed before unmounting.
> >> With systemd I'm seeing excessive reboot delays due to unmount timing out.
> > For example if you have a process started from NFS that has a log file on NFS
> > open, too.
> >> It seems the order is roughly like this:
> >> 1) Shutdown the network
> >> 2) Try unmounting filesystems, including NFS
> >> 3) Kill remaining processes
> >
> > I cannot confirm that, at least not for SLES/D 15. All mount units
> > for NFS filesystems created from fstab get "Before=remote-fs.target",
> > so they are shutdown before the network goes down. Check in
> > /run/systemd/generator to see if this entry is missing in your units.
>
> In SLES12 SP4 (originally reported for SP3) I have:
> # Automatically generated by systemd-fstab-generator
>
> [Unit]
> SourcePath=/etc/fstab
> Documentation=man:fstab(5) man:systemd-fstab-generator(8)
> Before=remote-fs.target
>
> [Mount]
> What=server:/exports/home
> Where=/home
> Type=nfs

Note that PID 1 adds in further, automatic dependencies that just
these. See "systemctl show home.mount -p After".

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel