There are two machines: (a) is the NFS server and (b) is the NFS client.
When machine (a) reboots is there a way to recover the NFS client on machine (b) without a reboot?

  • What OS is running on the NFS client? What errors are you seeing? – Mark Plotnick Dec 28 '15 at 16:44
  • Fedora 15 and 22. Not really seeing any errors, but if I ls the mount point the shell just hangs there. – user800133 Dec 28 '15 at 16:56
  • Is there anything in the system logs on the clients detailing the NFS errors? – Mark Plotnick Dec 28 '15 at 17:01
  • Curious if the server is OK after the reboot. On a client that is hanging, can you successfully manually mount the server's filesystem on a different mount point? – Mark Plotnick Dec 28 '15 at 17:03
  • I'm seeing this error in Dec 29 21:49:08 localhost kernel: [133067.342478] nfs: server <server hostname> not responding, still trying on the client. – user800133 Dec 30 '15 at 5:59

I don't understand what you mean by the word recover but if you mean to remount then yes, it is as simple as sudo mount -a.

  • Thanks, but I'm not using fstab. I just run mount manually. – user800133 Dec 28 '15 at 16:58
  • 1
    well then maybe you should. – Digisec Dec 28 '15 at 16:59
  • 1
    should it not be mount -a -o remount? – Rui F Ribeiro Dec 28 '15 at 17:20
  • You can do a remount if you want but if the server was rebooted, it is a good chance that the mount is lost, if it isn't then I would only remount that instead of everything. – Digisec Dec 28 '15 at 17:36

You can try a umount -f mountpoint

I have seen this a lot on my RHEL 7 machines connected to a Windows NFS server. The umount command will fail, but it will release whatever is keeping the client from operating.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.