Avocent CCM User Manual
Page 123
Appendices 109
91
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
has 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.
92
The attributes compared were the same as provided in the client’s request. This error is returned by
the NVERIFY operation.
93
An 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.
94
A lease has expired that is being used in the current operation.
95
A read or write operation was attempted on a locked file.
96
The server is in its recovery or grace period, which should match the server’s lease period.
97
The file handle provided is volatile and has expired at the server.
98
At attempt to OPEN a file with a share reservation has failed because of a share conflict.
99
The 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.
100
The SETCLIENTID operation has found that a client ID is already in use by another client.
101
The server has exhausted available resources while processing the COMPOUND procedure, and
cannot continue processing operations within the COMPOUND procedure.
102
The file system that contains the current file handle object has been relocated or migrated to another
server. The client may determine the new file system location by obtaining the fs_locations attribute
for the current file handle.
103
The logical current file handle value (or the saved file handle value in the case of RESTOREFH) has
not 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).
104
The server has received a request that specifies an unsupported minor version. The server must
return a COMPOUND4res with a zero length operation result array.
105
A client ID not recognized by the server was used in a locking or SETCLIENTID_CONFIRM request.
106
A state ID generated by an earlier server instance was used.
107
A state ID that designates the locking state for a lockowner-file at an earlier time was used.
Table D.1: NFS Error Codes (Continued)
Error
Code
Description