Enum ZeroFsError 

pub enum ZeroFsError {
    NotFound {
        path: String,
    },
    PermissionDenied {
        path: String,
    },
    NotPermitted {
        path: String,
    },
    AlreadyExists {
        path: String,
    },
    NotADirectory {
        path: String,
    },
    IsADirectory {
        path: String,
    },
    DirectoryNotEmpty {
        path: String,
    },
    NameTooLong {
        name: String,
    },
    InvalidArgument {
        message: String,
    },
    TooManySymlinks {
        path: String,
    },
    Closed,
    ConnectFailed {
        message: String,
    },
    NotLeader {
        path: String,
    },
    Stale {
        path: String,
    },
    Io {
        errno: i32,
        path: String,
        message: String,
    },
    Protocol {
        message: String,
    },
}

The single error type: flat and exhaustive (deliberately NOT #[non_exhaustive], so zerofs-ffi can apply uniffi remote derives and match exhaustively; a new variant must break its build, not silently degrade to a catch-all).

path/name payloads are lossy display strings (invalid bytes become U+FFFD), never round-trippable inputs.

The variant↔errno table is strict and 1:1; every server errno without a dedicated variant surfaces as ZeroFsError::Io verbatim, so ZeroFsError::to_errno is lossless by construction.

Variants

NotFound

No entry at the path (ENOENT).

Fields

path: String

The path the operation targeted (lossy display).

PermissionDenied

Access denied by permission bits (EACCES).

Fields

path: String

The path the operation targeted (lossy display).

NotPermitted

EPERM, distinct from EACCES: the operation requires ownership or privilege (e.g. chown by a non-owner).

Fields

path: String

The path the operation targeted (lossy display).

AlreadyExists

The target already exists (EEXIST).

Fields

path: String

The path the operation targeted (lossy display).

NotADirectory

A path component is not a directory (ENOTDIR).

Fields

path: String

The path the operation targeted (lossy display).

IsADirectory

The target is a directory where a non-directory was required (EISDIR).

Fields

path: String

The path the operation targeted (lossy display).

DirectoryNotEmpty

A directory removal found the directory non-empty (ENOTEMPTY).

Fields

path: String

The path the operation targeted (lossy display).

NameTooLong

Name exceeds 255 bytes.

Fields

name: String

The offending name (lossy display).

InvalidArgument

Bad input detected client-side (e.g. .. component, conflicting open options) or EINVAL from the server.

Fields

message: String

What was wrong with the input.

TooManySymlinks

Symlink resolution exceeded the 40-hop cap (cycle or pathological chain).

Fields

path: String

The path whose resolution looped (lossy display).

Closed

Handle or client used after close().

ConnectFailed

The initial connection or attach failed (including connect timeout expiry). Connectivity errors only ever surface here: after a successful connect, calls block through outages instead of failing.

Fields

message: String

What failed during connect/attach.

NotLeader

The node served the op but is no longer the HA leader (P9_ENOTLEADER): its lease has lapsed or it was fenced by a takeover. Re-routing to the current leader and retrying is safe; a crate::FailoverClient does so transparently.

Fields

path: String

The path the operation targeted (lossy display).

Stale

Stale handle (ESTALE). From crate::File::sync_all/crate::File::sync_data this is the durability signal: the .zerofs4 lineage broke (a failover the surviving node could not prove it inherited), so every write acked on this handle before the fsync may not be durable. Treat those writes as lost, redo them, and fsync again. From other operations it is a plain stale inode/handle (re-open the path).

Fields

path: String

The path the operation targeted (lossy display).

Io

Any other server errno, preserved verbatim.

Fields

errno: i32

The Linux errno the server returned.

path: String

The path the operation targeted (lossy display).

message: String

Human-readable rendering of the errno.

Protocol

Wire-level failure: codec error, unexpected reply type, failed negotiation.

Fields

message: String

What went wrong on the wire.

Implementations

impl ZeroFsError

pub fn to_errno(&self) -> i32

Linux errno per the strict 1:1 table; Io returns its errno unchanged.

Trait Implementations

impl Clone for ZeroFsError

fn clone(&self) -> ZeroFsError

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ZeroFsError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Display for ZeroFsError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Error for ZeroFsError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

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

Provides type-based access to context intended for error reports.

impl From<ZeroFsError> for Error

Lossless conversion for interop with std/tokio I/O: the errno round-trips through from_raw_os_error (so ErrorKind is set), and the original ZeroFsError is preserved as the source (recoverable via downcast).

fn from(e: ZeroFsError) -> Self

Converts to this type from the input type.