Clarify disk-full error messages
CHANGELOG · original
Improved disk-full handling: a Bash command cut off by a full disk now says so and names the folder to free up, and starting on a full temp volume prints a clear message, not a raw ENOSPC error Open official changelog ↗ Documentation
Documentation excerpt
Disk full or disk quota used up
Free up space, inodes, or disk quota on the volume that holds Claude Code's temporary directory. A line in a command's result starting Disk full:, Disk quota used up:, or Nearly out of inodes: names that directory.
Claude Code saves each Bash and PowerShell command's output to a file under that directory. If it can't create that file because the volume or your quota on it is full, your command doesn't start, and the result Claude reads is:
The command was not started: this computer's disk is full (ENOSPC) on the volume holding /tmp/claude-501 (Claude Code's temporary directory), so the file that captures command output could not be created there and nothing ran. Free space on that volume, or restart Claude Code with CLAUDE_CODE_TMPDIR set to a directory on another one, then retry. If this is the user's own computer, tell them before deleting anything to make room.
The Disk full:, Disk quota used up:, and Nearly out of inodes: messages follow a command that ran and exited with a nonzero code. For example:
Disk full: this computer's volume holding /tmp/claude-501 (Claude Code's temporary directory) has 3 MB free, so whatever this command printed was lost and its own writes may have failed with "No space left on device". Free space on that volume, or restart Claude Code with CLAUDE_CODE_TMPDIR set to a directory on another one, then retry. If this is the user's own computer, tell them before deleting anything to make room.
What to do:
- On macOS and Linux, run
df -h <dir>in your shell to see which volume holds the directory and how full it is.df -i <dir>shows how many inodes are free.<dir>is the directory your message names, as indf -i /tmp/claude-501 Disk full: this computer's volumeordisk is full (ENOSPC): anywhere on that volume, delete files you don't needDisk quota used up:,disk quota is used up (EDQUOT), orDisk full: a test write: delete your own files on that volume, even if it still shows free spaceNearly out of inodes:: delete many files on that volume. Each takes one inode whatever its size, so their number matters, not their size- Or restart Claude Code with
CLAUDE_CODE_TMPDIRset to a directory on a volume with room - Then have Claude run the command again
Before v2.1.309, the messages read as follows, and the same steps apply:
Your disk quota is full on the filesystem with Claude Code's temp directory <dir> (EDQUOT)The filesystem with Claude Code's temp directory <dir>, or your disk quota on it, is full (ENOSPC)Command output was lost: the temp filesystem at <dir> is fullor... is out of inodesThe command was not started: this computer's disk is full (ENOSPC), so the file that captures command output could not be created. Nothing ran., or the same with(EDQUOT). This form names no directory: look on the volume holding your system temp directory, such as/tmp, or the directory set inCLAUDE_CODE_TMPDIR
Before v2.1.305, a command that Claude Code couldn't start because the disk was full returned only the operating system's error text. That text read, for example, ENOSPC: no space left on device, open <path>.output.
Documentation snapshot · 2026-11-20