[systemd-devel] umount NFS problem

[Lennart Poettering]

On Fr, 05.04.19 08:28, Harald Dunkel (harald.dunkel at aixigo.de) wrote:
65;5403;1c
> Hi folks,
>
> I've got a device-busy-problem with /home, mounted via NFS.
> Shutdown of the host takes more than 180 secs. See attached
> log file.
>
> Apparently the umount of /home at 81925.154995 failed, (device
> busy, in my case it was a lost gpg-agent). This error was
> ignored, the NFS framework was shut down, the network was
> stopped, and then it was too late to properly handle the /home
> mount point.
>
> AFAIK the mount units are generated from /etc/fstab, so I wonder
> if this could be improved?
>
> The hosts (about 50 developer PCs) are running Debian 9, systemd
> 232-25+deb9u9. Unfortunately we are bound to this platform at
> least for another year.
>
>
> Every helpful hint is highly appreciated.

For some reason a number of X session processes stick around to the
very end and thus keep your /home busy.

[82021.052357] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[82021.101976] systemd-shutdown[1]: Sending SIGKILL to PID 2513 (gpg-agent).
[82021.130507] systemd-shutdown[1]: Sending SIGKILL to PID 2886 (xstartup).
[82021.158510] systemd-shutdown[1]: Sending SIGKILL to PID 2896 (xstartup).
[82021.186052] systemd-shutdown[1]: Sending SIGKILL to PID 2959 (xterm).
[82021.213129] systemd-shutdown[1]: Sending SIGKILL to PID 2960 (xterm).
[82021.239971] systemd-shutdown[1]: Sending SIGKILL to PID 2961 (xterm).
[82021.266285] systemd-shutdown[1]: Sending SIGKILL to PID 2966 (bash).
[82021.292234] systemd-shutdown[1]: Sending SIGKILL to PID 2967 (bash).
[82021.318061] systemd-shutdown[1]: Sending SIGKILL to PID 9146 (utempter).
[82021.343331] systemd-shutdown[1]: Sending SIGKILL to PID 9147 (utempter).

The question is how though. How do you start your X session? gdm?
startx from the console?

Lennart

--
Lennart Poettering, Berlin