http://bugzilla.opensuse.org/show_bug.cgi?id=973078 http://bugzilla.opensuse.org/show_bug.cgi?id=973078#c1 Chenzi Cao changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |rlmu@suse.com |ovo.novell.com | --- Comment #1 from Chenzi Cao --- Hi Mu Lei, please take a look at this issue, if you are not the right assignee, please feel free to reassign, thank you! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=973078 http://bugzilla.opensuse.org/show_bug.cgi?id=973078#c3 --- Comment #3 from Michal Hlavac --- (In reply to Mu Lei from comment #2)

Does it work fine sometimes, but occasionally shutdown earlier? IMO there's a suspended backport patch is needed for proper NFS service start. But it's delayed to upgrade in SLE12-sp2 first.

(In reply to Michal Hlavac from comment #0)

...

Created attachment 670838 [details] systemd log

I have 2 NFS mounts and sometimes (when reboot takes longer e.g. after tumbleweed snapshot upgrade), it looks like network or NFS daemon is shut down earlier then networkManager script (/etc/NetworkManager/dispatcher.d/nfs) is run to unmount NFS disks.

systemd log from shutdown is in attachment.

Yes, it mostly works fine. But this problem occurs on shutdown phase. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=973078 http://bugzilla.opensuse.org/show_bug.cgi?id=973078#c7 --- Comment #7 from Michal Hlavac --- (In reply to Dominique Leuenberger from comment #5)

NFS dispatcher does nothing else than

down) /bin/umount -alt nfs,nfs4

=> iof that hangs, then there is probably a deeper issue (there is still stuff in the mount table which wants to be unmounted)

I think problem is righ in this section. I think "down" is not proper way to umount nfs (or other) shares. Documentation (https://developer.gnome.org/NetworkManager/stable/NetworkManager.html) says: pre-down - The interface will be deactivated but has not yet been disconnected from the network. Scripts acting on this event must be placed or symlinked into the /etc/NetworkManager/dispatcher.d/pre-down.d directory, and NetworkManager will wait for script execution to complete before disconnecting the interface from its network. Note that this event is not emitted for forced disconnections, like when carrier is lost or a wireless signal fades. It is only emitted when there is an opportunity to cleanly handle a network disconnection event. down - The interface has been deactivated. So I think correct way is add umount section to /etc/NetworkManager/dispatcher.d/pre-down.d and do it before interafe is shutted down. -- You are receiving this mail because: You are on the CC list for the bug.