https://bugzilla.novell.com/show_bug.cgi?id=421556 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=421556#c1 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jw@novell.com --- Comment #1 from Neil Brown <nfbrown@novell.com> 2008-09-15 16:02:11 MDT --- This should be a non-issue for very recent kernels as processes stuck on an NFS mount of an unreachable server can now be killed. So there is not much value in fixing up the man page. What "mount -f" actually does is that it causes any pending requests to the server to fail, thus freeing up the processes so they can be killed. If the process immediately tried to access the filesystem again, it will lock up again. So a sequence of: - kill -9 any process using the mountpoint - umount -f - repeat should get the filesystem unmounted after a couple of cycles. An alternate approach is to either lazy-unmount (umount -l) the filesystem which will free up the mountpoint of a new mount, or mount --move olddir newdir to move the problematic mount out of the way. The latter is probably preferred as you can still try "umount -f" a few times while killing processes. Does that solve your problems? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.