The ESTALE error simply means that the server couldn't find any file for a given file handle.

A stale file handle is simply a file handle that points at a file that no longer exists on the server. This commonly happens because a user on one NFS client removes a file that a user on another client is in the middle of using. If both users are on the same NFS client, then the client moves the file to ".nfsXXX" instead of removing it, and the stale file handle problem doesn't occur. When the remove is from a different client, or from the server, then there is no way to detect what is happening and do the move, and that's when the stale file handle occurs.

Neither remounting nor rebooting fix the fundamental problem, which is that a file you want is gone. Of course, a reboot does have the side effect of blowing away any processes that were complaining, so it makes the ESTALE messages go away.

Check out the NOW web site @ now.netapp.com. You can find a wealth of information on this subject.

http://now.netapp.com/NOW/knowledge/contents/FAQ/FAQ_529.shtml

Abe. ----

Edward Hibbert wrote:

We're using HP machines running HP 11 against a NetApp, using NFS. We are occasionally seeing ESTALE errors on file I/O operations. This may be a problem in the application, but I'd welcome any information any of you have on just what ESTALE means. I've seen it described as occurring when an NFS client uses an invalid file handle, but I've also seen reference to it occurring when machines are rebooted.

So, my rather vague question is: what do you all know about ESTALE?

Edward Hibbert Internet Applications Group Data Connection Ltd Tel: +44 131 662 1212 Fax: +44 131 662 1345 Email: eh@dataconnection.com Web: http://www.dataconnection.com

-- ******************************* Ibrahima Bah (abe@netapp.com) Network Appliance, Inc. *******************************