| Previous | Next |
| STATUS_RANGE_NOT_LOCKED | STATUS_SERVER_DISABLED |
STATUS_DISK_FULL
STATUS_DISK_FULL means that a write, allocation, extension, or metadata update could not obtain the storage it needs. The visible free-space figure is not always the whole story: quotas can limit a specific user even when the volume still has free capacity, and thinly provisioned or virtual storage can run out of physical backing space behind an apparently larger logical volume.
What to check before retrying
- Measure both the caller's available space and the volume's actual free space. Windows quota guidance notes that a caller can receive a disk-full result after exceeding its allowance even when space remains for other users.
- Check the target directory, temp directory, log directory, and any staging volume separately; the failing allocation may not be on the volume the user expects.
- For virtual or thinly provisioned storage, inspect the backing pool, snapshot growth, and allocation policy.
- Verify whether the application writes temporary copies or expands a file before replacing the old version.
Application handling
Stop the current write cleanly and preserve an unambiguous record of which data was committed. A blind retry can repeatedly consume temporary space or leave partially written output. Use preflight capacity checks only as an optimization: another writer can consume the space between the check and the actual allocation.
See Windows disk-quota guidance, CreateFile, and the NTSTATUS reference.
Looking for a different code? Search another status or error code.