Umounting NFS Device without rebooting after a remote system fail
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can someone advise me of a way to unmount nfs devices without
rebooting after an nfs server has become unavailable.
Every time one of my nfs servers locks up, the computers the
terminals that had been using the mounts become hung. If I type in df
on one of the other machine, that terminal will hang. If I try to
umount the device it'll give the error:
umount: /mnt: device is busy
It's not possible to unmount the device because something had be
using it. Since the terminals were telnet sessions, I kill all the
login sessions that had had access to the device. It's still not
possible to unmount the device. The only way I can recover the ability
to use the df command (as well as others that might test that mounted
device), the terminal will hang.
umount -f
umount -r (to change it to read-only which I was hoping would notify the system that everything was flushed and updated then allow the umount to proceed)
umount -aft nfs (to umount everything)
Also, the nfs system that had failed is back up. I would have thought that the nfs becoming available would have wokeup the hung processes.
I keep locking up terminals because I have a habit of typing df -v for no reason and unconscienciously. It's like a fill-in while I'm thinking of another command to type when I'm working.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.