[systemd-devel] Antw: failing unmounts during reboot

[Lennart Poettering]

On Mo, 29.07.19 08:38, Ulrich Windl (Ulrich.Windl at rz.uni-regensburg.de) wrote:

> 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.
> ... 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.
> ...
> 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.
>
> I don't understand.
> 2019-04-17T13:20:01.313610+02:00 v04 systemd[32708]: Stopped target Default.
> 2019-04-17T13:20:01.320158+02:00 v04 systemd[32708]: Stopped target Basic System.
> 2019-04-17T13:20:01.320715+02:00 v04 systemd[32708]: Stopped target Paths.
> 2019-04-17T13:20:01.321092+02:00 v04 systemd[32708]: Stopped target Sockets.
> 2019-04-17T13:20:01.321459+02:00 v04 systemd[32708]: Stopped target Timers.
> 2019-04-17T13:20:01.321835+02:00 v04 systemd[32708]: Reached target Shutdown.
> 2019-04-17T13:20:01.322197+02:00 v04 systemd[32708]: Starting Exit the Session...

Please have a look at
https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1.

i.e. turn on debugging log output via kernel cmdline option and
collect the data in the shutdown hook. This should be helpful.

Lennart

--
Lennart Poettering, Berlin