HP 16-port SCS Installation Instructions Manual page 91

Table 6-5 NFS error codes
Error code Description
67 The operation was not allowed because the caller does not have the correct permission to perform the
requested operation. (This error differs from error 63, which is restricted to owner or privileged user permission
failures.)
68 The specified file already exists.
69 For NFSv3: An attempt was made to perform a cross-device hard link.
For NFSv4: An attempt was made to perform an operation between different FSIDs.
70 The specified device could not be located.
71 The caller specified a non-directory in a directory operation.
72 The caller specified a directory in a non-directory operation.
73 An invalid argument or unsupported argument was supplied for an operation. For example, attempting a
READLINK on an object other than a symbolic link.
NFSv3 example: Attempting to SETATTR with a time field on a server that does not support the operation.
NFSv4 example: Specifying a value for an enum field that is not defined in the protocol (such as nfs_ftype4).
74 For NFSv2: The operation caused a file to grow beyond the server's limit.
For NFSv3 and NFSv4: The operation would have caused a file to grow beyond the server limit.
75 For NFSv2: The operation caused the server file system to reach its limit.
For NFSv3 and NFSv4: The operation would have caused the server file system to exceed its limit.
76 For NFSv2: A write operation was attempted on a read-only file system.
For NFSv3 and NFSv4: A modifying operation was attempted on a read-only file system.
77 For NFSv3 and NFSv4: Too many hard links exist.
78 The file name in the operation was too long.
79 An attempt was made to remove a directory that was not empty.
80 For NFSv2: The client's disk quota on the server has been exceeded.
For NFSv3 and NFSv4: The user's resource limit on the server has been exceeded.
81 The file handle specified in the arguments was invalid. It either no longer exists or access to it has been
revoked.
82 The file handle specified in the arguments referenced a file on a non-local file system on the server (that is,
there were too many levels of remote in the path).
83 The server write cache used in the WRITECACHE call was flushed to the disk.
84 The file handle failed internal consistency checks.
85 An update synchronization mismatch was detected during a SETADDR operation.
86 For NFSv3, the READDIR or READDIRPLUS cookie is stale.
For NFSv4, the READDIR cookie is stale.
87 The operation is not supported.
88 For NFSv3: The buffer or request is too small.
For NFSv4: The encoded response to a READDIR request exceeds the size limit set by the initial request.
89 An error occurred in the server that does not map to any of the legal NFS protocol error values. The client
should translate this into an appropriate error. UNIX clients may choose to translate this to Event Input/Output
(EIO).
90 An attempt was made to create an object of a type not supported by the server.
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 might 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.
Technical specifications 85