Menu

1 / 2

“No space left on device” on RunPod: What Causes It and How to Fix It Before Billing Starts

DEV Community: machinelearning·Francisco Booth·6 days ago
#fJBDuTpb
Reading 0:00
15s threshold

You rent a GPU on RunPod, download your model, start fine-tuning. Everything looks fine until the job crashes:

OSError: [Errno 28] No space left on device

Or your training completes but GGUF export fails:

RuntimeError: [Errno 28] No space left on device

You have spent money on GPU compute, potentially hours of training, and now you cannot finish the job.

Having a large storage volume attached does not mean every process is using it. Here is why it happens, how to diagnose it, and how to catch it before the next run starts billing.

Why RunPod pods run out of disk

RunPod pods have two storage layers:

Container disk (/): Fast, small (typically 10–20GB on standard templates), wiped when the pod stops.

Network volume (/workspace): Persistent, sized by you when you create it.

The problem is that several things write to container disk by default even when a network volume is attached:

HuggingFace model cache (~/.cache/huggingface unless HF_HOME is set)

Training checkpoints (most frameworks default to…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.