Arch Linux

pausch

Member

Registered: 2012-01-08

Posts: 17

Shutdown issues because of network mounts

Hello everyone,

I know there are a lot of threads covering this topic but i am not satisfied with reading them (or i did not find the "one" ;-) ).

Currently I am mounting my network drives via /etc/fstab as NFS drive. This is the fstab entry:

wdmycloud:/nfs /mnt/net  nfs rw,user,noauto,soft,bg,intr,x-systemd.automount 0 0

But even with using this "x-systemd.automount" option, systemd has this "A stop job is running for /mnt/net/..." message with a timeout of 1:30 at shutdown when i do not manually umount the shares before shutting down the system. This is really annoying.

I read about this message being related to shutting down NetworkManager before unmounting these directories.

I also tried autofs instead and there the same problem occurred as well...

What can i do? Is forcing the unmount really the only working way?

Thank you for your help.

Nice New Year's Eve tomorrow!

Paul

PS. I hope that i have chosen the right forum. If not, please move this thread to the correct one!

Last edited by pausch (2014-12-30 13:32:42)

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: Shutdown issues because of network mounts

Maybe you should use a native systemd mount unit rather than an fstab entry for this.  Then you have give it explicit ordering.  I would venture to guess that if you were to make it 'After=NetworkManager.service' then during shutdown, it goes in reverse order and the mount would be stopped (unmounted) before NetworkManager is stopped.