Red Hat Bugzilla – Bug 337981
VFS: Busy inodes after unmount following NFS problems
Last modified: 2008-01-24 15:51:23 EST
Description of problem:
Following some trouble with remote NFS (v3) file systems, the machine crashed
having logged the following message:
VFS: Busy inodes after unmount of 0:1f. Self-destruct in 5 seconds. Have a nice
Version-Release number of selected component (if applicable):
This was a single crash, probably provoked by very special circumstances
Steps that led to the crash:
User tries to access a stale NFS mount:
The user tried to clear the stale mount by unmounting:
This failed with 'device is busy'. Locating the processes that were keeping the
stale mount busy, the user tried to kill them, eventually resorting to
kill -9 pid...
The processes went away and
succeeeded. The filesystem was then remounted:
mount server:/path/to/files /path1
The original job could then be performed, and the file system unmounted:
# do stuff...
Another NFS filesystem was then mounted:
mount server:/path/to/more/files /path2
Files were written to the /path2 tree without error
Finally, the user did:
At this point, the machine crashed. We don't know when the 'have a nice day'
message was logged relative to the crash.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
*** This bug has been marked as a duplicate of 253663 ***