[systemd-devel] Antw: failing unmounts during reboot

[Andrei Borzenkov]

29.07.2019 9:38, Ulrich Windl пишет:
>>>> Ulrich Windl schrieb am 29.07.2019 um 08:23 in Nachricht <5D3E90D1.4EC : 161 :
> 60728>:
>>>>> Frank Steiner <fsteiner-mail1 at bio.ifi.lmu.de> schrieb am 25.07.2019 um 14:14 in
>> Nachricht <913a3c04-a666-b44b-c6ec-fe3d8a7fe95e at bio.ifi.lmu.de>:
>>> 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
> 
> Sorry I hit "send" too quickly:
> That would mean the problem of not being unable to umnount /home is not that the network is down, but that some process still has open  files on /home.
> 
> However from the original problem report:
> 
> [  OK  ] Stopped target Host and Network Name Lookups. 
> 		 Stopping Name Service Cache Daemon... 
> [  OK  ] Stopped target Network. 
> 		 Stopping wicked managed network interfaces... 
> [  OK  ] Stopped Name Service Cache Daemon. 
> [  OK  ] Stopped wicked managed network interfaces. 
> 		 Stopping wicked network nanny service... 
> [  OK  ] Stopped Check if the profile matches the system. 
> [  OK  ] Stopped wicked network nanny service. 
> 		 Stopping wicked network management service daemon... 
> [  OK  ] Stopped wicked network management service daemon. 
> 		 Stopping wicked DHCPv4 supplicant service... 
> 		 Stopping wicked AutoIPv4 supplicant service... 
> 		 Stopping wicked DHCPv6 supplicant service... 
> [  OK  ] Stopped wicked DHCPv4 supplicant service. 
> [  OK  ] Stopped wicked DHCPv6 supplicant service. 
> [  OK  ] Stopped wicked AutoIPv4 supplicant service. 
> 		 Stopping D-Bus System Message Bus... 
> [  OK  ] Stopped SuSEfirewall2 phase 1. 
> [  OK  ] Stopped D-Bus System Message Bus. 
> [  OK  ] Stopped target Basic System. 
> [  OK  ] Stopped target Sockets. 

Stopping (or at least attempt to stop) /home should have happened before
these lines.

> ... I would call that a "network shutdown"...
> [  OK  ] Stopped target Host and Network Name Lookups. 
> 		 Stopping Name Service Cache Daemon... 
> [  OK  ] Stopped target Network. 
> 		 Stopping wicked managed network interfaces... 
> [  OK  ] Stopped Name Service Cache Daemon. 
> [  OK  ] Stopped wicked managed network interfaces. 
> 		 Stopping wicked network nanny service... 
> [  OK  ] Stopped Check if the profile matches the system. 
> [  OK  ] Stopped wicked network nanny service. 
> 		 Stopping wicked network management service daemon... 
> [  OK  ] Stopped wicked network management service daemon. 
> 		 Stopping wicked DHCPv4 supplicant service... 
> 		 Stopping wicked AutoIPv4 supplicant service... 
> 		 Stopping wicked DHCPv6 supplicant service... 
> [  OK  ] Stopped wicked DHCPv4 supplicant service. 
> [  OK  ] Stopped wicked DHCPv6 supplicant service. 
> [  OK  ] Stopped wicked AutoIPv4 supplicant service. 
> 		 Stopping D-Bus System Message Bus... 
> [  OK  ] Stopped SuSEfirewall2 phase 1. 
> [  OK  ] Stopped D-Bus System Message Bus. 
> [  OK  ] Stopped target Basic System. 
> [  OK  ] Stopped target Sockets. 

Do you really have identical lines second time in your log?

You need to provide full "systemctl show home.mount" and complete log
from boot to shutdown.

> ...
> I don't see unmounting of /home at all. The unmount errors reported were:
> ...
> [  OK  ] Unmounted Lock Directory. 
> [FAILED] Failed unmounting Runtime Directory. 
> 		 Unmounting /var... 
> [  OK  ] Unmounted /opt. 
> [  OK  ] Stopped File System Check on /dev/v04/opt. 
> [FAILED] Failed unmounting /var. 
> [  OK  ] Stopped File System Check on /dev/v04/var. 
> (The /var thing has different reasons)
> ...
> [  OK  ] Stopped Remount Root and Kernel File Systems. 
> [  OK  ] Reached target Shutdown. 
> ...At this point nothing more happened...
> Shutdown did not complete within two and a half minute.
> 

And what evidence you have that it is related to /home not being unmounted?