2

After an unscheduled reboot of our NFS server last night, a few of the clients reported "Stale NFS file handle".

All but one of these were fine after a reboot though one client is still giving errors after several reboots and manual umount/mounting of the filesystem.

What might be causing this be, and what could be done about it?

The OS is Ubuntu 10.04, with NFSv3.

Improve this question
1
  • Is the error you are still seeing after reboots and remounts "stale file handle", or is it another error?
    – sciurus
    Mar 31, 2011 at 13:41

1 Answer 1

Reset to default
1

NFS locks can survive a reboot. They should eventually timeout, but sometime you need to shutdown NFS and clear the lock directory manually.

I believe I usually run into this issue when the export is not available when the system comes back up. If I remember right the locks are maintained in /var/lib/nfs/sm.

Improve this answer
2
  • They did eventually clear. I can't tell if your suggestions of /var/lib/nfs/sm is right, but thanks.
    – jpnp
    Apr 21, 2011 at 14:18
  • @jpnp: I believe the timeouts are quite long. I was never able to wait for them to timeout.
    – BillThor
    Apr 21, 2011 at 15:38

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .