Probable cause: This failure can happen because of the following reasons:

1. The Kerberos Dynamic Load Library could not be loaded by the NFS client.
2. The kerberos context could not be created by the NFS client.
3. The GSS credentials for the NFS client's Kerberos Principal could not be obtained.

Action: Check your kerberos configurations, fix any configuration issues identified, restart the NFS client and retry the operation. Contact the system programmer if the problem persists.

Action: Increase the value of the timeo client attribute on the mount command.

Probable cause: An attempt was made to perform an operation limited to processes with appropriate privileges or to the owner of a file or other resource.

Action: Ensure that uid and gid are correct.

Probable cause: A component of a specified path name does not exist, or the path name is an empty string.

Action: Ensure that the file/directory exists.

Probable cause: Some physical input or output error occurred.

Action: No action required.

Probable cause: Input or output on a special file refers to a device that does not exist, or makes a request beyond the capabilities of the device. It may also occur when, for example, a tape drive is not on-line.

Action: Ensure that the mount address is correct.

Probable cause: An attempt was made to access a file in a way forbidden by its file access permissions.

Action: Verify that the correct access authority is being requested.

Probable cause: An existing file/dir was mentioned in an inappropriate context; for example, as a new link name in the link function.

Action: Try to use another file/dir name.

Probable cause: A hard link to a file on another file system was attempted.

Action: Ensure that the link is correct.

Probable cause: An attempt was made to apply an inappropriate function to a device; for example, trying to read a write-only device such as printer.

Action: Ensure that the command parameters are correct.

Probable cause: A component of the specified path name exists, but it is not a directory, when a directory was expected.

Action: Ensure that the specified path name is correct.

Probable cause: An attempt was made to open a directory with write mode specified.

Action: Ensure that the access mode is correct.

Probable cause: Some invalid argument was supplied, source had an invalid superblock or, a remount was attempted, while source was not already mounted on target.

Action: Ensure that the arguments are correct. If remount is used, determine that the mount command was made.

Probable cause: The size of a file would exceed the maximum file size of implementation or offset maximum established in the corresponding file description.

Action: Operate with files that satisfy maximum file size requirement and use offsets that satisfy maximum offset requirement.

Probable cause: During the write function on a regular file or when extending a directory, there is no free space left on the device.

Action: Use another directory or device for store file or clear hash/garbage (be sure that these data are useless).

Probable cause: An attempt was made to modify a file or directory on a file system that is read only.

Action: Ensure that you have sufficient privileges.

Probable cause: An attempt was made to have the link count of a single file exceed (LINK_MAX).

Action: –

Probable cause: The length of a pathname exceeds (PATH_MAX), or a pathname component is longer than (NAME_MAX) and (_POSIX_NO_TRUNC) was in effect for that file.

Action: Use names that correspond with filename requirements.

Probable cause: A directory with entries other than dot and dot-dot was supplied when an empty directory was expected.

Action: Ensure that the directory is empty.

Probable cause: The user’s quota of disk blocks or user’s quota of inodes was exhausted.

Action: Ensure that free space is available on the disk.

Probable cause: An attempt was made to access an open file (on an NFS file system) which is now unavailable as referenced by the file descriptor. This may indicate the file was deleted on the NFS server or some other catastrophic event occurred.

Action: Ensure that file was not deleted on the NFS server.

Probable cause: Server made attempt to handle an NFS request by generating a request to another NFS server, which is not allowed.

Action: No action required.

Probable cause: A file descriptor argument is out of range, refers to no open file, or a read (write) request is made to a file that is only open for writing (reading).

Action: Ensure that the descriptor is right.

Probable cause: Update synchronization mismatch was detected during a SETATTR operation.

Action: –

Probable cause: READDIR cookie is stale.

Action: Retry the read dir operation.

Probable cause: An attempt was made to use a function or operation that is not available in this implementation.

Action: Ensure that the operation is available and the command is right.

Probable cause: Insufficient buffer resources were available in the system to perform the socket operation.

Action: Increase the size of the socket buffers.

Probable cause: An error occurred on the server which does not map to any of the legal NFS version 4 protocol error values.

Action: –

Probable cause: The named file is a character-special or block-special file and the associated device does not exist.

Action: Ensure that the mount address is correct.

Probable cause: The server initiated the request, but was not able to complete it in a timely fashion.

Action: No action required. (This is a temporary condition and later calls to the same routine may complete normally.)

Probable cause: This error is returned by the NVERIFY operation to signify that the attributes compared were the same as provided in the client request.

Action: No action required.

Probable cause: A system-imposed limit on the number of simultaneous file locks was reached.

Action: Wait and retry the operation.

Probable cause: A lease has expired that is being used in the current operation.

Action: Retry the operation.

Probable cause: A read/write operation was attempted on a locked file.

Action: Wait and retry the operation.

Probable cause: This server is in its recovery or grace period which should match the lease period of the server.

Action: Wait and retry the operation.

Probable cause: The file handle provided is volatile and has expired at the server.

Action: Try to remount.

Probable cause: An attempt to OPEN a file with a share reservation has failed because of a share conflict.

Action: Solve a share conflict.

Probable cause: An open with write mode has been attempted to a write protected tape.

Action: Ensure that the user has sufficient privileges.

Probable cause: The SETCLIENTID operation has found that a client id is already in use by another client.

Action: Try to remount.

Probable cause: Requested resource, such as a lock or a process, is temporarily unavailable.

Action: Retry the operation. (This is a temporary condition and later calls to the same routine may complete normally.)

Probable cause: The file system that contains the current file handle object is not present at the server. It may have been relocated, migrated to another server or may have never been present. The client may obtain the new file system location by obtaining the "fs_locations" attribute for the current file handle.

Action: No action required.

Probable cause: The logical current file handle value (or, in the case of RESTOREFH, the saved file handle value) has not been set properly. This may be a result of a malformed COMPOUND operation (that is, no PUTFH or PUTROOTFH before an operation that requires the current file handle be set).

Action: Try to remount.

Probable cause: The server has received a request that specifies an unsupported minor version. The server must return a COMPOUND4res with a zero length operations result array.

Action: No action required.

Probable cause: A clientid not recognized by the server was used in a locking or SETCLIENTID_CONFIRM request.

Action: Try to remount.

Probable cause: A stateid generated by an earlier server instance was used.

Action: Try to remount.

Probable cause: A stateid that designates the locking state for a lockowner-file at an earlier time was used.

Action: Try to remount.

Probable cause: A stateid generated by the current server instance, but which does not designate any locking state (either current or superseded) for current lockowner-file pair, was used.

Action: Try to remount.

Probable cause: The sequence number in a locking request is neither the next expected number or the last number processed.

Action: No action required.

Probable cause: This error is returned by the VERIFY operation to signify that the attributes compared were not the same as provided in the client’s request.

Action: No action required.

Probable cause: 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.

Action: No action required.

Probable cause: The current file handle provided for a LOOKUP is not a directory but a symbolic link. Also used if the final component of the OPEN path is a symbolic link.

Action: Ensure that the path name is correct.

Probable cause: The RESTOREFH operation does not have a saved file handle (identified by SAVEFH) to operate upon.

Action: No action required.

Probable cause: A lease being renewed is associated with a file system that has been migrated to a new server.

Action: No action required.

Probable cause: An attribute specified is not supported by the server. Does not apply to the GETATTR operation.

Action: No action required.

Probable cause: A reclaim of client state was attempted in circumstances in which the server cannot guarantee that conflicting state has not been provided to another client. This can occur because the reclaim has been done outside of the grace period of the server, after the client has done a RECLAIM_COMPLETE operation, or because previous operations have created a situation in which the server is not able to determine that a reclaim-interfering edge condition does not exist.

Action: No action required.

Probable cause: The reclaim provided by the client does not match any of the server’s state consistency checks and is bad.

Action: No action required.

Probable cause: The reclaim provided by the client has encountered a conflict and cannot be provided. Potentially indicates a misbehaving client.

Action: No action required.

Probable cause: The server encountered an XDR decoding error while processing an operation.

Action: No action required.

Probable cause: A CLOSE was attempted and file locks would exist after the CLOSE.

Action: No action required.

Probable cause: The client attempted a READ, WRITE, LOCK or SETATTR operation not sanctioned by the stateid passed (for example, writing to a file opened only for read).

Action: Ensure that the user has sufficient privileges.

Probable cause: An owner, owner_group, or ACL attribute value can not be translated to local representation.

Action: No action required.

Probable cause: A UTF-8 string contains a character which is not supported by the server in the context in which it being used.

Action: Use correct character encoding symbols.

Probable cause: A name string in a request consists of valid UTF-8 characters supported by the server but the name is not supported by the server as a valid name for current operation.

Action: Change the name on supported by the server.

Probable cause: The result of the function is too large (overflow) or too small (underflow) to be represented in the available space.

Action: No action required.

Probable cause: –

Action: No action required.

Probable cause: An illegal operation value has been specified in the argop field of a COMPOUND or CB_COMPOUND procedure.

Action: Ensure that the operation is correct.

Probable cause: An attempt was made to lock a system resource that would have resulted in a deadlock situation.

Action: No action required.

Probable cause: The operation cannot be successfully processed because a file involved in the operation is currently open.

Action: Ensure that the appropriate file is not opened. Then retry the operation.

Probable cause: Due to administrator intervention, the lock owner’s record locks, share reservations, and delegations have been revoked by the server.

Action: No action required. Consult with the server’s administrator.

Probable cause:

Action: –