Bug#798314: systemd: Systemd waits 30 minutes to shut down because of NFS share

[Kiko Piris]

On 07/09/2015 at 21:33 -0300, Javier Ayres wrote:

> The drive is mounted correctly at startup, but if I don't manually unmount it
> before shutting down the system will take 30 minutes to shut down. The message
> "A stop job is running for /mnt/D3 (0s / 1min 30s)" is shown; after 90 seconds
> it changes to something like "A stop job is running for /mnt/D3 (1min 30s /
> 3min)" and it keeps incrementing until 30 minutes have passed. I changed the
> fstab entry to:

Hi,

I’m also experiencing this with my laptop (up-2-date Debian sid).

I don’t use NetworkManager (my Wi-Fi configuration is written directly
in /etc/network/interfaces).

I have 3 nfs shares from my home nas mounted on the laptop. I have those
neverending “A stop job is running for…” messages for all 3 of them (I
haven’t had the patience to wait half an hour to see if the shutdown
finishes).

However, I’ve seen that not 100% of the times shutdown gets stuck there
(when shutting down with the remote shares mounted, I mean).

I’ve seen that, sometimes, if I manually umount the shares and then
mount them again later, then the following shutdown sometimes finishes
without locking.

Is there anything I can do or any information I can provide to help?

Thanks!

-- 
Kiko