Type Alias IoErrorKind 

pub type IoErrorKind = ErrorKind;

A kind of I/O error

Aliased Type

pub enum IoErrorKind {
    NotFound,
    PermissionDenied,
    ConnectionRefused,
    ConnectionReset,
    HostUnreachable,
    NetworkUnreachable,
    ConnectionAborted,
    NotConnected,
    AddrInUse,
    AddrNotAvailable,
    NetworkDown,
    BrokenPipe,
    AlreadyExists,
    WouldBlock,
    NotADirectory,
    IsADirectory,
    DirectoryNotEmpty,
    ReadOnlyFilesystem,
    FilesystemLoop,
    StaleNetworkFileHandle,
    InvalidInput,
    InvalidData,
    TimedOut,
    WriteZero,
    StorageFull,
    NotSeekable,
    QuotaExceeded,
    FileTooLarge,
    ResourceBusy,
    ExecutableFileBusy,
    Deadlock,
    CrossesDevices,
    TooManyLinks,
    InvalidFilename,
    ArgumentListTooLong,
    Interrupted,
    Unsupported,
    UnexpectedEof,
    OutOfMemory,
    InProgress,
    Other,
}

Variants

NotFound

An entity was not found, often a file.

PermissionDenied

The operation lacked the necessary privileges to complete.

ConnectionRefused

The connection was refused by the remote server.

ConnectionReset

The connection was reset by the remote server.

HostUnreachable

The remote host is not reachable.

NetworkUnreachable

The network containing the remote host is not reachable.

ConnectionAborted

The connection was aborted (terminated) by the remote server.

NotConnected

The network operation failed because it was not connected yet.

AddrInUse

A socket address could not be bound because the address is already in use elsewhere.

AddrNotAvailable

A nonexistent interface was requested or the requested address was not local.

NetworkDown

The system’s networking is down.

BrokenPipe

The operation failed because a pipe was closed.

AlreadyExists

An entity already exists, often a file.

WouldBlock

The operation needs to block to complete, but the blocking operation was requested to not occur.

NotADirectory

A filesystem object is, unexpectedly, not a directory.

For example, a filesystem path was specified where one of the intermediate directory components was, in fact, a plain file.

IsADirectory

The filesystem object is, unexpectedly, a directory.

A directory was specified when a non-directory was expected.

DirectoryNotEmpty

A non-empty directory was specified where an empty directory was expected.

ReadOnlyFilesystem

The filesystem or storage medium is read-only, but a write operation was attempted.

FilesystemLoop

🔬This is a nightly-only experimental API. (io_error_more)

Loop in the filesystem or IO subsystem; often, too many levels of symbolic links.

There was a loop (or excessively long chain) resolving a filesystem object or file IO object.

On Unix this is usually the result of a symbolic link loop; or, of exceeding the system-specific limit on the depth of symlink traversal.

StaleNetworkFileHandle

Stale network file handle.

With some network filesystems, notably NFS, an open file (or directory) can be invalidated by problems with the network or server.

InvalidInput

A parameter was incorrect.

InvalidData

Data not valid for the operation were encountered.

Unlike InvalidInput, this typically means that the operation parameters were valid, however the error was caused by malformed input data.

For example, a function that reads a file into a string will error with InvalidData if the file’s contents are not valid UTF-8.

TimedOut

The I/O operation’s timeout expired, causing it to be canceled.

WriteZero

An error returned when an operation could not be completed because a call to write returned Ok(0).

This typically means that an operation could only succeed if it wrote a particular number of bytes but only a smaller number of bytes could be written.

StorageFull

The underlying storage (typically, a filesystem) is full.

This does not include out of quota errors.

NotSeekable

Seek on unseekable file.

Seeking was attempted on an open file handle which is not suitable for seeking - for example, on Unix, a named pipe opened with File::open.

QuotaExceeded

Filesystem quota or some other kind of quota was exceeded.

FileTooLarge

File larger than allowed or supported.

This might arise from a hard limit of the underlying filesystem or file access API, or from an administratively imposed resource limitation. Simple disk full, and out of quota, have their own errors.

ResourceBusy

Resource is busy.

ExecutableFileBusy

Executable file is busy.

An attempt was made to write to a file which is also in use as a running program. (Not all operating systems detect this situation.)

Deadlock

Deadlock (avoided).

A file locking operation would result in deadlock. This situation is typically detected, if at all, on a best-effort basis.

CrossesDevices

Cross-device or cross-filesystem (hard) link or rename.

TooManyLinks

Too many (hard) links to the same filesystem object.

The filesystem does not support making so many hardlinks to the same file.

InvalidFilename

A filename was invalid.

This error can also occur if a length limit for a name was exceeded.

ArgumentListTooLong

Program argument list too long.

When trying to run an external program, a system or process limit on the size of the arguments would have been exceeded.

Interrupted

This operation was interrupted.

Interrupted operations can typically be retried.

Unsupported

This operation is unsupported on this platform.

This means that the operation can never succeed.

UnexpectedEof

An error returned when an operation could not be completed because an “end of file” was reached prematurely.

This typically means that an operation could only succeed if it read a particular number of bytes but only a smaller number of bytes could be read.

OutOfMemory

An operation could not be completed, because it failed to allocate enough memory.

InProgress

🔬This is a nightly-only experimental API. (io_error_inprogress)

The operation was partially successful and needs to be checked later on due to not blocking.

Other

A custom error that does not fall under any other I/O error kind.

This can be used to construct your own [Error]s that do not match any [ErrorKind].

This [ErrorKind] is not used by the standard library.

Errors from the standard library that do not fall under any of the I/O error kinds cannot be matched on, and will only match a wildcard (_) pattern. New [ErrorKind]s might be added in the future for some of those.