Open System Services NFS Management and Operations Guide

C NFS Protocol Version 2 Errors and Mount Protocol
Version 1 Errors
This appendix contains the message text, causes, recovery actions, and corresponding error
numbers for NFS protocol version 2 (NFS2) and mount protocol version 1 (MNT1) errors. These
errors are not returned in individual EMS messages from the OSS NFS manager process. Instead,
all these errors are reported in a single EMS message type, NFS E00003 (see Appendix A
(page 78)). This message contains an error value that corresponds to the error names listed here.
For example, an NFS error 00003 message reporting an NFS2 error with an errnum of 13 refers
to NFS2 Error 13.
NFS2 Errors
In these descriptions of NFS2 errors, note that the values that follow include the BUSY (16), INVAL
(22), and OPNOTSUPP (45) errors. Although these errors are not defined in version 2 of the NFS
protocol, they are included here because they are commonly used error numbers that are returned
by many NFS servers and expected by many NFS clients.
NFS2 Error 1
No permission match. The caller does not have the ownership necessary
to perform the requested operation.
Cause
An attempt was made to perform an NFS operation on a file, but the current ownership of the
file caused the attempted operation to be denied because:
• A caller other than the file’s owner or a super-group user attempts to change the file
ownership of an NFS file.
• An attempt is made to change the file attributes of a file in a way prohibited by the current
security settings.
Effect
Attempted operation fails.
Recovery
The recommended action depends on the cause of the error:
• If the attempted operation was denied because of the file’s ownership, either the caller must
change to a user ID that is recognized as valid for the operation on the file or the owner
of the file must change the file’s ownership to allow the caller access.
• If the attempted operation was denied because of security settings, either the caller must
change to a user ID that is recognized as valid for the operation on the file or the security
settings must be changed (by a user with appropriate permission) to allow the caller access.
NFS2 Error 2
No such file or directory. The specified file or directory does not
exist.
Cause
Either the filename or directory specified in an operation does not exist or one of the directories
specified in a pathname does not exist.
Effect
Attempted operation on the file or directory fails.
Recovery
Corrective action is application-dependent. If this error occurs during an attempt to remove a
file or directory, this error can be ignored because it can be caused by NFS retries. Otherwise,
NFS2 Errors 85