Red Hat Bugzilla – Bug 69890
netfs retry fails to unmount NFS file systems
Last modified: 2014-03-16 22:29:18 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
Description of problem:
netfs retry either fails to unmount NFS file systems, or when it does, it fails
to recognize that it succeeded and continues retrying the umount command. netfs
continues retrying even after the local portmap and lockd have gone away,
leaving meaningless errors on the console during shutdown.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up an ID with a home directory in NFS
2. log out (this leaves gconfd running in the backround)
3. immediately shut the system down
Actual Results: from /var/log/messages:
Jul 21 17:46:06 dexter umount: umount2: Device or resource busy
Jul 21 17:46:06 dexter umount: umount: /home: not mounted
Jul 21 17:46:06 dexter netfs: Unmounting NFS filesystems: failed
Jul 21 17:46:13 dexter netfs: Unmounting NFS filesystems (retry): succeeded
Jul 21 17:46:20 dexter netfs: Unmounting NFS filesystems (retry): succeeded
After killing all processes with TERM, netfs umount results in an
"RPC error 101" type message on the console.
Expected Results: If retrying "succeeded" why does it retry again?
Is there a way to prevent a retry after portmap is gone?
umount may not update /proc/mounts on error.
Using /etc/mtab or directly parsing the output of the mount command might be a
better idea than using /proc/mounts to determine which file systems are still
Part of the problem is that retrying to unmount NFS file systems continues
after NFS statd and the portmapper have shut down. Unmounting network
file systems needs to succeed before any network services go away, otherwise
there is no guarantee that hard mounted file systems will get all their
data written back to file servers.
This behavior only appears with the retail version of RH 7.3. I was experiencing
the same problems on my home machines. After installing all 7.3 errata (except
kernel updates), the problem seems to have disappeared.
Closing bugs on older, no longer supported, releases. Apologies for any lack of
If this persists on a current release, such as Fedora Core 4, please open a new bug.