Red Hat Bugzilla – Bug 1249644
umount network filesystems order slows shutdown procedure
Last modified: 2016-07-19 15:16:13 EDT
Network filesystems are schedule to bee unmounted after the network is shut down.
NetworkManager is already down and system keep trying to unmount nfs and samba shared for around 120 seconds per share.
Network filesystems should be unmounted before networkmanager.
They should already be ordered so: network mount units are ordered after network.target, and NetworkManager.service is ordered before network.target. Shutdown is performed in reverse, so network mounts are stopped first, then network.target, then NetworkManager.service.
Can you show the output of 'systemctl show -p Before,After,Wants xxx' for xxx being your network mounts (e.g. some-path.mount) and NetworkManager.service?
Here we go, system is a fedora 22 x86_64
[root@tiefighter ~]# systemctl show -p Before,After,Wants NetworkManager.service
Before=NetworkManager-wait-online.service network.target multi-user.target shutdown.target network.service
After=systemd-journald.socket system.slice basic.target netcf-transaction.service firewalld.service
[root@tiefighter ~]# systemctl show -p Before,After,Wants /media/multimedia
After=systemd-journald.socket system.slice network.target remote-fs-pre.target -.mount network-online.target
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.