Open System Services NFS Management and Operations Guide

Recovery
The pathname should be examined. If no condition exists where a symbolic link points to a
previously encountered symbolic link, the pathname should be respecified without the offending
symbolic link (ideally, by specifying the actual directory entry where the chain of symbolic links
was supposed to lead). If a loop condition exists, correct the condition and retry the request.
MNT1 Error 63
Name too long. The specified name contains more than the maximum number
of characters allowed.
Cause
This error occurs when a pathname or directory name is too long.
Effect
Attempted operation fails.
Recovery
Use a shorter name.
MNT1 Error 70
Stale fhandle. The caller specified an invalid file handle (fhandle).
Cause
The caller attempted to perform an operation using an invalid file handle. A file handle can
become invalid when the file to which it refers no longer exists or when the access permission
has changed in such a way that access by the caller is revoked. The most common causes are:
• An NFS client left an NFS mount active for a long time and the NFS services were brought
down and back up again during the interval.
• A particular directory was removed so that the caller’s current directory no longer exists.
Effect
Attempted operation fails.
Recovery
Try remounting the server or selecting a different working directory, and then retry the operation.
94 NFS Protocol Version 2 Errors and Mount Protocol Version 1 Errors