GNOME Bugzilla – Bug 677053
Suspend (sleep S3) makes NetworkManager to disconnect before/without unmounting NFS shares
Last modified: 2012-07-26 13:36:26 UTC
When an NFS share is mounted and the system is suspended then it seems to resume immediately but with NetworkManager already stopped, with network links disconnected. As consequence any further access to NFS shares will block the accessing processes and suspend gets interrupted (due to timeouts I guess). Restarting NetworkManager ("sudo service network-manager restart") unblocks those processes and (surprisingly) continues the previously interrupted suspend! I tried various NFS options like "soft" without success. Placing a script into /usr/lib/pm-utils/sleep.d/ to unmount NFS shares does not help either. I guess Networkmanager is suspended via dbus, before those scripts are executed. IMHO NetworkManager should care about NFS shares explicitly itself, or it should offer a way to add scripts that do this which are executed *BEFORE* network links are disconnected. If there are such a way, then please let me know! This bug is discussed downstream since 2010-02-03 on http://launchpad.net/bugs/516592
BTW: I also tried it once with a script in /etc/NetworkManager/dispatcher.d/ - without success. I see this bug with network-manager 0.8.4 in Ubuntu 11.04, and with 0.9.4 in Linux Mint 13.
dispatcher.d is the correct way. Is this still valid with 9.x?