Server, no longer refers to a valid file on the server. Where a file handle, which NFS uses to uniquely identify a file on the The error, ESTALE, was originally introduced to handle the situation a client has a file handle but the file got deleted on the server). A stale file handle easily happens with NFS (e.g. Note that mount yielding ESTALE is quite different from some other system call (like open/readdir/unlink/chdir. For example to do this with all exports: # exportfs -uaĪfter this the client's mount -t nfs. You can fix this via explicitly un-exporting and re-exporting the relevant exports on the server. If there is entry for the client it might be a stale one. You can check for this via looking at /proc/fs/nfs/exports or /proc/fs/nfsd/exports. When the server is back and the client then umounts and tries to mount the nfs volume the server might respond with: mount.nfs: Stale file handle A mount -t nfs fails with Stale file handle if the server has some stale exports entries for that client.Įxample scenario: this might happen when the server reboots without the client umounting the nfs volumes first.
0 Comments
Leave a Reply. |