Filesystem quota
A filesystem quota accounts for and can limit storage usage by a user, group or project within a filesystem.
Space and inode limits are distinct. With enforcement active, a soft limit permits an excess for a grace period, subject to the hard limit and other constraints. After expiry, further allocation of that resource is blocked until usage falls below the soft limit or policy changes. Hard-limit privilege exceptions depend on the implementation. [2] [1]
XFS separates quota accounting from enforcement, so recorded usage alone does not show that allocation limits are active. [4] Linux write() reports exhausted block quota as EDQUOT, separately from ENOSPC for insufficient data space. [3]
Relations
- related
- statvfs, Inode, File preallocation, Thin provisioning
Limitations
- An allocation ceiling is not a reservation of capacity in the filesystem or its backing thin pool. [5]
Citations
- Linux man-pages: quotactl(2), user, group and project limits
- Linux kernel: quota subsystem, space/inode limits and grace periods
- Linux man-pages: write(2), EDQUOT, ENOSPC and partial writes
- XFS: xfs_quota(8), accounting versus enforcement
- Hesela: filesystem quotas and capacity headroom
Sources & caveats
- Linux API and quota documentation review; supported quota types and enforcement depend on the filesystem. [1]