Avocent CCM - Manual (Page 124)

110 CCM Installer/User Guide
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 lock owner 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.
124
A name string in a request contains valid UTF-8 characters supported by the server, but the name is
not supported by the server as a valid name for the current operation.
125
The range for a LOCK, LOCKT or LOCKU operation is not appropriate for the allowable range of
offsets for the server.
126 The server does not support the atomic upgrade or downgrade of locks.
Table D.1: NFS Error Codes (Continued)
Error
Code
Description