| Previous | Next |
| EUSERS | ESTALE |
EDQUOT
Quota exhaustion is not the same as a full volume
EDQUOT means that the relevant quota has been reached. A volume can still report free blocks or free inodes while a particular user, group, project, or policy scope cannot allocate more. That distinction matters because deleting unrelated data elsewhere on the filesystem may not release the quota that blocked this operation.
Record the target filesystem, owner identity, requested allocation, and whether the operation was creating data, extending a file, or adding metadata. Compare EDQUOT with ENOSPC: the latter is global filesystem capacity exhaustion; the former is an allocation policy for the affected principal or scope.
Useful evidence
- Collect available space and inode information together with quota status for the effective owner.
- Check whether writes, xattr updates, or copy-on-write operations account against different resource pools.
- Keep the failed byte count and file offset; a partial write can leave a valid prefix that needs application-specific recovery.
References
Looking for a different code? Search another status or error code.