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 return the line, 'umount.nfs: Server failed to unmount '192.168.0.2:/home/o/files/downloads'', but this is only because it cannot override an fstab entry. So to repeat, this is not a bug, merely an unfriendliness, and if someone can delete this report to spare other devs wasting time reading it, I'd appreciate it. Thanks. -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
