rustfs/rustfs · error · DiskError
outdated XL meta
Error message
outdated XL meta
What it means
Raised when an object's xl.meta read back does not match the expected metadata version/state — typically a concurrent write replaced the metadata between read and compare, or the meta on disk is stale relative to the request.
Source
Thrown at crates/ecstore/src/disk/error.rs:128
#[error("path not found")]
PathNotFound,
#[error("volume not found")]
VolumeNotFound,
#[error("volume is not empty")]
VolumeNotEmpty,
#[error("volume access denied")]
VolumeAccessDenied,
#[error("disk access denied")]
FileAccessDenied,
#[error("file is corrupted")]
FileCorrupt,
#[error("short write")]
ShortWrite,
#[error("bit-rot hash algorithm is invalid")]
BitrotHashAlgoInvalid,
/// Never constructed locally by RustFS (only reachable through wire
/// decoding, and no current node sends it). The wire code is kept for
/// cross-version compatibility — do not renumber or remove (backlog#1831).
#[error("Rename across devices not allowed, please fix your backend configuration")]
CrossDeviceLink,
#[error("less data available than what was requested")]
LessData,
#[error("more data was sent than what was advertised")]
MoreData,
#[error("outdated XL meta")]View on GitHub (pinned to 5dca076efe)
Solutions
- Re-read the object metadata and retry the operation with fresh state
- Check for concurrent writers on the same object version
- If persistent, inspect for corrupted xl.meta and trigger healing
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at crates/ecstore/src/disk/error.rs:128 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of rustfs/rustfs@5dca076efe (2026-08-20).
Data as JSON: /api/errors/8201707983efdd8b.
Report an issue: GitHub.