DeepSpeed ZeRO-Offload NVMe aio_write failed: No space left on device

DeepSpeed ZeRO-Offload filled the NVMe filesystem used for optimizer or parameter swap. The failed aio_write means the offload state is incomplete, even if the training process reports a later optimizer error. This entry explains how to confirm the cause, apply the fix, and separate it from adjacent deepspeed failures.

Symptom

DeepSpeed ZeRO-Offload NVMe aio_write failed: No space left on device

Root cause

DeepSpeed ZeRO-Offload filled the NVMe filesystem used for optimizer or parameter swap. The failed aio_write means the offload state is incomplete, even if the training process reports a later optimizer error. The decisive evidence is the first log line that precedes "DeepSpeed ZeRO-Offload NVMe aio_write failed: No space left on device" and differs from a healthy run.

Recommended fix

stop the run, inspect free bytes and inodes on the configured nvme_path, and remove only stale offload data from jobs that are no longer active.

How Denpex helps

Denpex investigates DeepSpeed ZeRO-Offload NVMe aio_write failed: No space left on device using the evidence you provide or your connected workload collects. Earlier rank, host or application evidence is needed to distinguish an initiating failure from a downstream report.

The literal signature is "DeepSpeed ZeRO-Offload NVMe aio_write failed: No space left on device". It is a distributed training failure associated with DeepSpeed ZeRO and optimizer sharding. The line identifies the failing operation or subsystem, while the surrounding evidence decides whether it is the initiating fault or a downstream symptom.

DeepSpeed ZeRO-Offload filled the NVMe filesystem used for optimizer or parameter swap. The failed aio_write means the offload state is incomplete, even if the training process reports a later optimizer error. The failure becomes visible at this call site because the operation first requires the missing resource, valid state, healthy peer, or correct result. Earlier log lines and a known-good control carry more causal value than the final wrapper exception.

• The workload stops or loses forward progress after emitting "DeepSpeed ZeRO-Offload NVMe aio_write failed: No space left on device".
• A retry on the same configuration reproduces the failure because the causal state has not changed.
• The outer framework exception can hide the rank, node, allocation, or dependency that failed first.
• Increasing timeouts or reducing workload size can suppress the symptom without correcting the cause.

• DeepSpeed ZeRO and optimizer sharding
• production-shaped multi-accelerator workloads
• containerized and bare-metal deployments of the same stack

Use this checklist to test the hypothesis against a small reproduction. No single line proves the root cause, so preserve the preceding events and compare one variable at a time.

• ✓Find the first occurrence of "DeepSpeed ZeRO-Offload NVMe aio_write failed: No space left on device" and preserve at least 100 lines before it.
• ✓Identify which rank, node, device, or process emitted the first related warning.
• ✓calculate the expected parameter and optimizer offload footprint for every local rank, then compare it with filesystem capacity and quota. Confirm ranks are not writing duplicate state into an unintended shared path.
• ✓Repeat the same input after the targeted change and require the signature to disappear.
• ✓Resume from last complete checkpoint after the NVMe offload path is healthy only after the control passes.

• DeepSpeed ZeRO-Offload filled the NVMe filesystem used for optimizer or parameter swap. The failed aio_write means the offload state is incomplete, even if the training process reports a later optimizer error.
• The decisive evidence is the first log line that precedes "DeepSpeed ZeRO-Offload NVMe aio_write failed: No space left on device" and differs from a healthy run.
• A nearby failure remains a competing hypothesis until a control separates configuration, capacity, transport, and hardware causes.

DeepSpeed ZeRO-Offload NVMe aio_write failed: No space left on device

Use this text as a lookup key in logs and upstream issue trackers. It is not presented as a captured customer log. Confirm the cause from your own preceding events, versions, configuration and the cited references.

stop the run, inspect free bytes and inodes on the configured nvme_path, and remove only stale offload data from jobs that are no longer active. This changes the condition in the causal diagnosis instead of hiding the outer exception. The repeated control proves ownership before recovery from last complete checkpoint after the NVMe offload path is healthy.

# Preserve evidence before restarting
rg -n -i 'error|exception|timeout|failed' <log-file>
nvidia-smi
python -m torch.utils.collect_env

# Find the exact signature in the complete log
rg -n -F -- "DeepSpeed ZeRO-Offload NVMe aio_write failed: No space left on device" <log-file>

Adapt the snippet to your framework. The same pattern holds for PyTorch Lightning, Hugging Face Trainer, DeepSpeed, Megatron-LM, and vLLM training wrappers. Where the wrapper exposes a config flag (for examplelr_scheduler_type in Trainer), prefer the flag over the imperative API to keep the schedule declarative and reproducible.

Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.

DeepSpeed changes when parameters, gradients and optimizer state are created, partitioned, gathered and offloaded. The hub separates ZeRO, memory, checkpoint and pipeline failures by lifecycle phase.