nfs
NFS Error Codes
Error codes returned by the Network File System protocol, covering NFSv3 (symbolic names prefixed NFS3ERR_) as defined in RFC 1813 and NFSv4 (prefixed NFS4ERR_) as defined in RFC 7530.
93 codes
· All codes 93 codes
- NFS3ERR_ACCES Permission denied The caller does not have the correct permission to perform the requested operation. This error is returned when the caller does not have access permission for the file system object.
- NFS3ERR_BAD_COOKIE READDIR or READDIRPLUS cookie is stale The cookie passed in a READDIR or READDIRPLUS request is no longer valid, typically because the directory was modified.
- NFS3ERR_BADHANDLE Illegal NFS file handle The file handle fails internal consistency checks.
- NFS3ERR_BADTYPE An object of an invalid type was specified An attempt was made to create an object of a type not supported by the server.
- NFS3ERR_DQUOT Disk quota exceeded The operation would have caused the user's disk quota to be exceeded on the server.
- NFS3ERR_EXIST File exists The file specified already exists.
- NFS3ERR_FBIG File too large The operation would have caused a file to grow beyond the server's limit for maximum file size.
- NFS3ERR_INVAL Invalid argument Some argument is invalid, such as an invalid filehandle or an out-of-range offset.
- NFS3ERR_IO I/O error A hard error occurred when the operation was in progress. This error may be unrecoverable.
- NFS3ERR_ISDIR Is a directory The caller specified a non-directory in an operation that requires a non-directory.
- NFS3ERR_JUKEBOX Request initiated but not completed The server initiated the request but was not able to complete it in time, typically because the file is on slow media such as tape or optical disk.
- NFS3ERR_MLINK Too many hard links The operation would have caused the maximum number of hard links to a file to be exceeded.
- NFS3ERR_NAMETOOLONG Filename too long The length of the filename exceeded the maximum limit allowed by the server.
- NFS3ERR_NODEV No such device An operation was requested that requires a device and no such device exists.
- NFS3ERR_NOENT No such file or directory The file or directory name specified does not exist.
- NFS3ERR_NOSPC No space left on device The operation would have caused the server's file system to exceed its limit.
- NFS3ERR_NOT_SYNC Update synchronization mismatch An update was attempted on a file that was not in sync with the server's version of that file.
- NFS3ERR_NOTDIR Not a directory A directory component in a pathname was not, in fact, a directory.
- NFS3ERR_NOTEMPTY Directory not empty An attempt was made to remove a directory that was not empty.
- NFS3ERR_NOTSUPP Operation is not supported The server does not support the requested operation.
- NFS3ERR_NXIO No such device or address No such device or address. The file is a block or character special device and no corresponding device exists on the server.
- NFS3ERR_PERM Not owner The caller does not have correct ownership to perform the requested operation.
- NFS3ERR_REMOTE Object is remote The file system object is on a remote machine and cannot be accessed by the server.
- NFS3ERR_ROFS Read-only file system A modifying operation was attempted on a read-only file system.
- NFS3ERR_SERVERFAULT An error occurred on the server An error occurred on the server which does not map to any of the legal NFS version 3 protocol error values.
- NFS3ERR_STALE Stale file handle The file handle given in the arguments was invalid. The file referred to by that file handle no longer exists or has been deleted.
- NFS3ERR_TOOSMALL Buffer or request is too small The server's response would have exceeded the client's buffer or the request was too small to fit the response.
- NFS3ERR_XDEV Attempt to do a cross-device hard link An attempt was made to create a hard link across file system boundaries.
- NFS4ERR_ACCESS Permission denied The caller does not have the correct permission to perform the requested operation.
- NFS4ERR_ADMIN_REVOKED Lock administratively revoked A lock or open state was revoked by the server administrator; the client must reclaim or reacquire state.
- NFS4ERR_ATTRNOTSUPP Attribute not supported An attribute specified in the request is not supported by the server.
- NFS4ERR_BAD_COOKIE READDIR cookie is stale The cookie passed in a READDIR request is no longer valid, typically because the directory was modified.
- NFS4ERR_BAD_RANGE Bad lock range The lock range specified is not valid, such as a zero-length range.
- NFS4ERR_BAD_SEQID Bad sequence ID The sequence ID in the request is not the next expected sequence ID for the given open or lock owner.
- NFS4ERR_BAD_STATEID Bad state ID The stateid provided is invalid; it is not associated with the current file, open owner, or lock owner.
- NFS4ERR_BADCHAR Bad character in string The string supplied contains a character that is not supported in the context in which it was used.
- NFS4ERR_BADHANDLE Illegal NFS file handle The file handle fails internal consistency checks.
- NFS4ERR_BADNAME Bad name The name specified is invalid, such as containing a null character or path separator.
- NFS4ERR_BADOWNER Invalid owner or group The owner or group specified in the attribute is not valid on the server.
- NFS4ERR_BADTYPE Invalid object type An attempt was made to create an object of a type not supported by the server.
- NFS4ERR_BADXDR Bad XDR encoding The request contains an XDR encoding error, which could not be decoded by the server.
- NFS4ERR_CB_PATH_DOWN Callback path down The client's callback path is not available; the server cannot send callback operations to this client.
- NFS4ERR_CLID_INUSE Client ID already in use The client ID provided in a SETCLIENTID call is already in use by another client.
- NFS4ERR_DEADLOCK Deadlock detected A lock request would cause a deadlock; the client should release some locks and retry.
- NFS4ERR_DELAY File not immediately available The server initiated the request but was not able to complete it immediately; the client should retry the operation.
- NFS4ERR_DENIED Lock unavailable A conflicting lock prevents the requested lock from being obtained; the client should try the request again.
- NFS4ERR_DQUOT Disk quota exceeded The operation would have caused the user's disk quota to be exceeded on the server.
- NFS4ERR_EXIST File exists The file specified already exists.
- NFS4ERR_EXPIRED Lock lease has expired The client's lock lease has expired, requiring state recovery.
- NFS4ERR_FBIG File too large The operation would have caused a file to grow beyond the server's limit for maximum file size.
- NFS4ERR_FHEXPIRED File handle has expired The file handle provided is volatile and has expired.
- NFS4ERR_FILE_OPEN File is open The operation is not permitted because the file is open by one or more clients.
- NFS4ERR_GRACE In grace period The server is in the grace period following a restart and the client must wait before retrying new lock requests.
- NFS4ERR_INVAL Invalid argument Some argument is invalid, such as an invalid filehandle or an out-of-range offset.
- NFS4ERR_IO I/O error A hard error occurred when the operation was in progress.
- NFS4ERR_ISDIR Is a directory The caller specified a directory in a non-directory operation.
- NFS4ERR_LEASE_MOVED Lease moved At least one file system associated with the client's lease has been moved to a different server.
- NFS4ERR_LOCK_NOTSUPP Locking not supported The server does not support locking for the file system object specified.
- NFS4ERR_LOCK_RANGE Lock range not supported The lock range requested overlaps with a region that is not lockable or exceeds server limits.
- NFS4ERR_LOCKED File is locked A read or write operation was attempted on a region of a file that is already locked by a conflicting lock.
- NFS4ERR_LOCKS_HELD Locks held Locks are held by the client and must be released before the operation can complete.
- NFS4ERR_MINOR_VERS_MISMATCH Minor version mismatch The server does not support the minor version specified in the COMPOUND procedure.
- NFS4ERR_MLINK Too many hard links The operation would have caused the maximum number of hard links to a file to be exceeded.
- NFS4ERR_MOVED File system moved The file system which contains the object has been moved to another server.
- NFS4ERR_NAMETOOLONG Filename too long The length of the filename exceeded the maximum limit allowed by the server.
- NFS4ERR_NO_GRACE No grace period The server is not in a grace period and reclaim operations cannot be performed.
- NFS4ERR_NOENT No such file or directory The file or directory name specified does not exist.
- NFS4ERR_NOFILEHANDLE No file handle The operation requires a current file handle to be set, but none was provided.
- NFS4ERR_NOSPC No space left on device The operation would have caused the server's file system to exceed its limit.
- NFS4ERR_NOT_SAME Attributes not the same The attributes of the object have changed since a previous operation relied on them being stable.
- NFS4ERR_NOTDIR Not a directory A directory component in a pathname was not, in fact, a directory.
- NFS4ERR_NOTEMPTY Directory not empty An attempt was made to remove a directory that was not empty.
- NFS4ERR_NOTSUPP Operation is not supported The server does not support the requested operation.
- NFS4ERR_NXIO No such device or address No such device or address.
- NFS4ERR_OLD_STATEID Old state ID The stateid provided is an old, out-of-sequence stateid that has already been superseded.
- NFS4ERR_OP_ILLEGAL Illegal operation The operation is not a legal NFSv4 operation.
- NFS4ERR_OPENMODE Incompatible open mode The current open mode for the file does not allow the operation being attempted (e.g., writing to a read-only open).
- NFS4ERR_PERM Not owner The caller does not have correct ownership to perform the requested operation.
- NFS4ERR_RECLAIM_BAD Reclaim bad A reclaim request was rejected because the server has no information about the client's previous state.
- NFS4ERR_RECLAIM_CONFLICT Reclaim conflict A reclaim was attempted for a file that another client has already reclaimed.
- NFS4ERR_RESOURCE Insufficient resources The server does not have sufficient resources to complete the requested operation.
- NFS4ERR_RESTOREFH No saved file handle A RESTOREFH operation was performed but no saved file handle exists from a prior SAVEFH operation.
- NFS4ERR_ROFS Read-only file system A modifying operation was attempted on a read-only file system.
- NFS4ERR_SAME Inode is the same The source and destination in a RENAME operation are the same file.
- NFS4ERR_SERVERFAULT Server fault An error occurred on the server which does not map to any of the legal NFSv4 protocol error values.
- NFS4ERR_SHARE_DENIED Share reservation conflict A OPEN request was denied because of a conflicting share reservation.
- NFS4ERR_STALE Stale file handle The file handle given in the arguments was invalid. The file referred to by that file handle no longer exists or has been deleted.
- NFS4ERR_STALE_CLIENTID Stale client ID The client ID provided is not valid or has been removed from the server's records.
- NFS4ERR_STALE_STATEID Stale state ID The stateid provided is no longer valid, likely because the server has been restarted.
- NFS4ERR_SYMLINK Inode is a symbolic link The current file handle is a symbolic link, which is not valid as a directory file handle for this operation.
- NFS4ERR_TOOSMALL Response too small The reply would have been larger than the client's buffer.
- NFS4ERR_WRONGSEC Wrong security flavor The security mechanism used by the client does not match the security mechanism required by the server for the exported file system.
- NFS4ERR_XDEV Attempt to do a cross-device hard link An attempt was made to create a hard link across file system boundaries.