I have a Windows NFS server and several CentOS linux servers which were mounting volumes from it. The Windows server moved to a new network and even though DNS works and the NFS mount was mounted by hostname, it appears the NFS client also makes note of the ipaddr value, which is no longer valid. This causes the typical hanging mounts, df, issues one would expect. How do I resolve this retroactively?

  • Did you try restarting networking? – sandyp Nov 18 '13 at 21:23

If the IP address has changed then you'll likely need to restart the NFS clients and/or run the umount command explicitly releasing the mounted service. This may not be able to complete though, with the original NFS service is now gone.

The only other approach that I was able to find was this one, written up in this Linux Journal article titled: How-To: Release Stuck NFS Mounts without a Reboot. I've never used this approach and until today never heard of this method but it does sound feasible in looking through it.

Also I believe you may run into issues depending on whether the NFS mount was mounted with intr/nointr. You can read more about this feature switch in the NFS man page, man nfs.


intr / nointr  Selects whether to allow signals to interrupt file operations 
               on this mount point. If neither option is specified (or if 
               nointr is specified), signals do  not  interrupt NFS file 
               operations. If intr is specified, system calls return EINTR 
               if an in-progress NFS operation is interrupted by a signal.

               Using the intr option is preferred to using the soft option 
               because it is significantly less likely to result in data

               The  intr  / nointr mount option is deprecated after kernel 
               2.6.25.  Only SIGKILL can interrupt a pending NFS operation 
               on these kernels, and if specified, this mount option is 
               ignored to provide backwards compatibility with older
  • How do you restart the NFS client? I know the server side, but don't think I ever needed to restart the client side. – Gregg Leventhal Nov 19 '13 at 15:11
  • @GreggLeventhal - they aren't directly client, more services that help facilitate NFS. /etc/init.d/nfslock is one of them. – slm Nov 19 '13 at 15:17
  • 1
    I used umount -l which allowed me to unmount the nfs volume. This solves my problem. – Gregg Leventhal Nov 19 '13 at 15:48
  • @GreggLeventhal - sorry I thought you had already tried umounting that, or I would've suggested that. I don't have the -l switch on any version I have of umount. What does the man page say it will do? – slm Nov 19 '13 at 18:10
  • I tried regular umount , -l is lazy which means it will unmount it first, then resolve open file handles and whatnot later when/if possible. – Gregg Leventhal Nov 19 '13 at 20:26

This Post has steps that have worked for me. In a nutshell:

  • Assign Old IP of NFS server to an alias. ifconfig eth0:fakenfs Old_IP netmask xxx.xxx.xxx.xxx
  • umount -l /mount
  • bring down the alias: ifconfig eth0:fakenfs down
  • Mount the NFS share again: mount -a

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.