This is a follow-up question to "Stale NFS file handle" after reboot

as its solution doesn't work for me.

My case is simple, after server rebooted, I'm getting "Stale file handle" on client side, even after

  • I umount all nfs mounts and remout them on client side. or,
  • On the NFS server UN-export and re-export the file system

I can control both end (and don't mind kill/restart anything), what's the simplest solution to overcome the above situation?

  • I would assume that the simplest solution is to restart the clients. Is that ruled out in your scenario? Nov 23, 2019 at 2:01
  • Yeah @HarryJohnston, I gave up and restart the client machine. And to my greatest surprise, I'm still getting "Stale file handle" on client side, despite that both server and client have now been restarted.
    – xpt
    Nov 23, 2019 at 5:46
  • Which filesystem is exported by the server? Does the client application uses locks?
    – kofemann
    Apr 11, 2020 at 8:13
  • The filesystem on both side (client & server) are both ext4. I don't think locks are used, because I'm actually sharing nfs4 as RO. Further it's the mpv the movie playing program that I used to access nfs4, which I believe is read-only and don't think it place any locks. Thanks @kofemann
    – xpt
    Apr 11, 2020 at 13:21


You must log in to answer this question.

Browse other questions tagged .