HP 16-port SCS Installation Instructions Manual page 92

Table 6-5 NFS error codes
Error code Description
93 An attempt to lock a file was denied. Because this might 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 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 might 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.
108 A state ID generated by the current server instance (that does not designate any locking state either current or
superseded) for a current lockowner file pair was used.
109 The sequence number in a locking request is neither the next expected number nor the last number processed.
110 The attributes compared were not the same as provided in the client's request. This error is returned by the
VERIFY operation.
111 A lock request is operating on a sub-range of a current lock for the lockowner and the server does not support
this type of request.
112 The current file handle provided for a LOOKUP is not a directory but a symbolic link. This error is also issued if
the final component of the OPEN path is a symbolic link.
113 The RESTOREFH operation does not have a saved file handle (identified by SAVEFH) to operate on.
114 A lease being renewed is associated with a file system that has been migrated to a new server.
115 A specified attribute is not supported by the server. This does not apply to the GETATTR operation.
116 A reclaim of the client state has fallen outside of the server's grace period. As a result, the server cannot
guarantee that a conflicting state has not been provided to another client.
117 The reclaim provided by the client does not match any of the server's state consistency checks and is bad.
118 The reclaim provided by the client has encountered a conflict and cannot be provided. This could indicate a
misbehaving client.
119 The server encountered an XDR decoding error while processing an operation.
120 A CLOSE was attempted and file locks would exist after the CLOSE.
121 The client attempted a READ, WRITE, LOCK, or SETATTR operation that was not sanctioned by the state ID
passed (for example, writing to a file opened only for reading).
122 An owner, owner group, or ACL attribute value cannot be translated to local representation.
123 A UTF-8 string contains a character that is not supported by the server in the context in which it is being used.
Technical specifications 86