Appendices 109
Table D.1: NFS Error Codes (Continued)
Error Description
Code
The server initiated the request, but was not able to complete in a timely manner. The client should wait and then try the request with a new RPC transaction ID. For example, this error should be returned from a server that supports hierarchical storage and receives a request to process a file that
91has been migrated. In this case, the server should start the immigration process and respond to the client with the error.
For NFSv4: this error may also occur when a necessary delegation recall makes processing a request in a timely manner impossible.
92The attributes compared were the same as provided in the client’s request. This error is returned by the NVERIFY operation.
93An attempt to lock a file was denied. Since this may be a temporary condition, the client is encouraged to retry the lock request until the lock is accepted.
94A lease has expired that is being used in the current operation.
95A read or write operation was attempted on a locked file.
96The server is in its recovery or grace period, which should match the server’s lease period.
97The file handle provided is volatile and has expired at the server.
98At attempt to OPEN a file with a share reservation has failed because of a share conflict.
99The security mechanism being used by the client for the operation does not match the server’s security policy. The client should change the security mechanism being used and retry the operation.
100The SETCLIENTID operation has found that a client ID is already in use by another client.
101The server has exhausted available resources while processing the COMPOUND procedure, and cannot continue processing operations within the COMPOUND procedure.
The file system that contains the current file handle object has been relocated or migrated to another
102server. The client may determine the new file system location by obtaining the fs_locations attribute for the current file handle.
The logical current file handle value (or the saved file handle value in the case of RESTOREFH) has
103not been properly set. This may have resulted from a malformed COMPOUND operation (that is, no PUTFH or PUTROOTFH before an operation that requires the current file handle to be set).
104The server has received a request that specifies an unsupported minor version. The server must return a COMPOUND4res with a zero length operation result array.
105A client ID not recognized by the server was used in a locking or SETCLIENTID_CONFIRM request.
106A state ID generated by an earlier server instance was used.
107A state ID that designates the locking state for a