- NFS3_OK
-
Indicates the call completed successfully.
- NFS3ERR_PERM
-
Not owner. The operation was not allowed because the
caller is either not a privileged user (root) or not the
owner of the target of the operation.
- NFS3ERR_NOENT
-
No such file or directory. The file or directory name
specified does not exist.
- NFS3ERR_IO
-
I/O error. A hard error (for example, a disk error)
occurred while processing the requested operation.
- NFS3ERR_NXIO
-
I/O error. No such device or address.
- NFS3ERR_ACCES
-
Permission denied. The caller does not have the correct
permission to perform the requested operation. Contrast
this with NFS3ERR_PERM, which restricts itself to owner
or privileged user permission failures.
- NFS3ERR_EXIST
-
File exists. The file specified already exists.
- NFS3ERR_XDEV
-
Attempt to do a cross-device hard link.
- NFS3ERR_NODEV
-
No such device.
- NFS3ERR_NOTDIR
-
Not a directory. The caller specified a non-directory in
a directory operation.
- NFS3ERR_ISDIR
-
Is a directory. The caller specified a directory in a
non-directory operation.
- NFS3ERR_INVAL
-
Invalid argument or unsupported argument for an
operation. Two examples are attempting a READLINK on an
object other than a symbolic link or attempting to
SETATTR a time field on a server that does not support
this operation.
- NFS3ERR_FBIG
-
File too large. The operation would have caused a file to
grow beyond the server's limit.
- NFS3ERR_NOSPC
-
No space left on device. The operation would have caused
the server's file system to exceed its limit.
- NFS3ERR_ROFS
-
Read-only file system. A modifying operation was
attempted on a read-only file system.
- NFS3ERR_MLINK
-
Too many hard links.
- NFS3ERR_NAMETOOLONG
-
The filename in an operation was too long.
- NFS3ERR_NOTEMPTY
-
An attempt was made to remove a directory that was not
empty.
- NFS3ERR_DQUOT
-
Resource (quota) hard limit exceeded. The user's resource
limit on the server has been exceeded.
- NFS3ERR_STALE
-
Invalid file handle. The file handle given in the
arguments was invalid. The file referred to by that file
handle no longer exists or access to it has been
revoked.
- NFS3ERR_REMOTE
-
Too many levels of remote in path. The file handle given
in the arguments referred to a file on a non-local file
system on the server.
- NFS3ERR_BADHANDLE
-
Illegal NFS file handle. The file handle failed internal
consistency checks.
- NFS3ERR_NOT_SYNC
-
Update synchronization mismatch was detected during a
SETATTR operation.
- NFS3ERR_BAD_COOKIE
-
READDIR or READDIRPLUS cookie is stale.
- NFS3ERR_NOTSUPP
-
Operation is not supported.
- NFS3ERR_TOOSMALL
-
Buffer or request is too small.
- NFS3ERR_SERVERFAULT
-
An error occurred on the server which does not map to any
of the legal NFS version 3 protocol error values. The
client should translate this into an appropriate error.
UNIX clients may choose to translate this to EIO.
- NFS3ERR_BADTYPE
-
An attempt was made to create an object of a type not
supported by the server.
- NFS3ERR_JUKEBOX
-
The server initiated the request, but was not able to
complete it in a timely fashion. 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 client with this error.
