How to Manage Linux File Quotas for Users

The Linux operating system manages file quotas through kernel-level accounting built into the filesystem layer, enabling administrators to restrict disk space consumption and file creation on a per-user or per-group basis. By tracking storage block allocations and inode generation, the system enforces configurable soft and hard thresholds across designated mount points. This article explains the underlying mechanisms of Linux disk quotas, the distinction between capacity and file-count limits, and the administrative commands used to initialize, configure, and enforce these storage boundaries.

Core Concepts: Space Limits vs. Inode Limits

Linux tracks two distinct metrics when applying storage quotas:

• Block Quotas (Disk Space): Restricts the total volume of data (measured in kilobytes or blocks) a user can write to the filesystem.
• Inode Quotas (File Count): Restricts the absolute number of files, directories, and links a user can create, regardless of the size of those files. This prevents users from exhausting the filesystem's inode table with millions of zero-byte files.

Soft Limits, Hard Limits, and Grace Periods

Quota limits are implemented in three operational tiers:

1. Soft Limit: A warning threshold. Users can exceed this limit temporarily. When passed, a countdown timer known as the grace period is triggered.
2. Grace Period: The time window (typically seven days by default) during which a user operating above the soft limit must reduce their usage.
3. Hard Limit: An absolute ceiling. Once a user hits the hard limit, the kernel immediately blocks any further disk allocation or file creation with an "out of disk space" error, even if the physical drive has free capacity. If the grace period expires while a user is still above the soft limit, the soft limit automatically becomes an enforced hard limit until space is reclaimed.

Enabling Quotas on the Filesystem

Quotas must be explicitly supported and enabled on the target partition. This configuration occurs in the /etc/fstab configuration file by appending quota mount options to the target filesystem:

• usrquota: Enables tracking and enforcement for individual users.
• grpquota: Enables tracking and enforcement for user groups.

Example /etc/fstab entry:

UUID=xxxx-xxxx-xxxx    /home    ext4    defaults,usrquota,grpquota    0    2

After modifying /etc/fstab, the filesystem must be remounted using mount -o remount /home to activate the kernel-level accounting flags.

Database Initialization and Maintenance

Linux maintains quota tracking tables at the root of the mounted filesystem (typically named aquota.user and aquota.group). These files are generated and updated using specific system utilities:

• quotacheck: Scans the filesystem to calculate current disk usage and builds or repairs the aquota binary database files. The typical execution flags are -cum /mountpoint to create new files and scan the system.
• quotaon and quotaoff: Activates or deactivates kernel enforcement of quotas on specified filesystems.

Modern filesystems like XFS handle quotas internally without requiring external aquota files, allowing quotas to be activated directly via mount options and managed via the xfs_quota tool.

Managing and Inspecting User Limits

System administrators manage active user parameters using a suite of dedicated command-line utilities:

• edquota: Opens an interactive text editor displaying the current block and inode counts alongside soft and hard limits for a specific user (e.g., edquota -u username). It can also modify grace periods via edquota -t.
• setquota: Allows automated, script-friendly configuration of limits from the command line without opening a text editor.
• repquota: Generates comprehensive reports summarizing disk usage and quota compliance for all users across a given filesystem.
• quota: Allows non-root users to view their own current resource limits and usage.