Closed report as requested by reporter.
** Changed in: ubuntu
Status: New = Invalid
--
Forced umount.nfs doesn't work
https://bugs.launchpad.net/bugs/162786
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Actually it's not a bug, and it does work.
'umount2: Device or resource busy' can be avoided by including
'hard,intr' in the NFS fstab line. Since the processes can now be
interrupted, the client's GUI file managers no longer hang after the
forcing umount.nfs.
The 'umount.nfs -f' will still
