Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 17. Disk Quotas

Disk space can be restricted by implementing disk quotas which alert a system administrator before a user consumes too much disk space or a partition becomes full.
Disk quotas can be configured for individual users as well as user groups. This makes it possible to manage the space allocated for user-specific files (such as email) separately from the space allocated to the projects a user works on (assuming the projects are given their own groups).
In addition, quotas can be set not just to control the number of disk blocks consumed but to control the number of inodes (data structures that contain information about files in UNIX file systems). Because inodes are used to contain file-related information, this allows control over the number of files that can be created.
The quota RPM must be installed to implement disk quotas.

Note

This chapter is for all file systems, however some file systems have their own quota management tools. See the corresponding description for the applicable file systems.
For XFS file systems, see Section 3.3, “XFS Quota Management”.
Btrfs does not have disk quotas so is not covered.

17.1. Configuring Disk Quotas
Copy link

To implement disk quotas, use the following steps:
  1. Enable quotas per file system by modifying the /etc/fstab file.
  2. Remount the file system(s).
  3. Create the quota database files and generate the disk usage table.
  4. Assign quota policies.
Each of these steps is discussed in detail in the following sections.

17.1.1. Enabling Quotas
Copy link

Procedure 17.1. Enabling Quotas

  1. Log in as root.
  2. Edit the /etc/fstab file.
  3. Add either the usrquota or grpquota or both options to the file systems that require quotas.

Example 17.1. Edit /etc/fstab

For example, to use the text editor vim type the following: 
# vim /etc/fstab
Copy to Clipboard Toggle word wrap

Example 17.2. Add Quotas

/dev/VolGroup00/LogVol00 /         ext3    defaults        1 1
LABEL=/boot              /boot     ext3    defaults        1 2
none                     /dev/pts  devpts  gid=5,mode=620  0 0
none                     /dev/shm  tmpfs   defaults        0 0
none                     /proc     proc    defaults        0 0
none                     /sys      sysfs   defaults        0 0
/dev/VolGroup00/LogVol02 /home     ext3    defaults,usrquota,grpquota  1 2
/dev/VolGroup00/LogVol01 swap      swap    defaults        0 0 . . .
Copy to Clipboard Toggle word wrap
In this example, the /home file system has both user and group quotas enabled.

Note

The following examples assume that a separate /home partition was created during the installation of Red Hat Enterprise Linux. The root (/) partition can be used for setting quota policies in the /etc/fstab file.

17.1.2. Remounting the File Systems
Copy link

After adding either the usrquota or grpquota or both options, remount each file system whose fstab entry has been modified. If the file system is not in use by any process, use one of the following methods:
  • Run the umount command followed by the mount command to remount the file system. See the man page for both umount and mount for the specific syntax for mounting and unmounting various file system types.
  • Run the mount -o remount file-system command (where file-system is the name of the file system) to remount the file system. For example, to remount the /home file system, run the mount -o remount /home command.
If the file system is currently in use, the easiest method for remounting the file system is to reboot the system.

17.1.3. Creating the Quota Database Files
Copy link

After each quota-enabled file system is remounted run the quotacheck command.
The quotacheck command examines quota-enabled file systems and builds a table of the current disk usage per file system. The table is then used to update the operating system's copy of disk usage. In addition, the file system's disk quota files are updated.

Note

The quotacheck command has no effect on XFS as the table of disk usage is completed automatically at mount time. See the man page xfs_quota(8) for more information.

Procedure 17.2. Creating the Quota Database Files

  1. Create the quota files on the file system using the following command: 
    # quotacheck -cug /file system
    Copy to Clipboard Toggle word wrap
  2. Generate the table of current disk usage per file system using the following command: 
    # quotacheck -avug
    Copy to Clipboard Toggle word wrap
Following are the options used to create quota files:
c
Specifies that the quota files should be created for each file system with quotas enable.
u
Checks for user quotas.
g
Checks for group quotas. If only -g is specified, only the group quota file is created.
If neither the -u or -g options are specified, only the user quota file is created.
The following options are used to generate the table of current disk usage:
a
Check all quota-enabled, locally-mounted file systems
v
Display verbose status information as the quota check proceeds
u
Check user disk quota information
g
Check group disk quota information
After quotacheck has finished running, the quota files corresponding to the enabled quotas (either user or group or both) are populated with data for each quota-enabled locally-mounted file system such as /home.

17.1.4. Assigning Quotas per User
Copy link

The last step is assigning the disk quotas with the edquota command.
Prerequisite
  • User must exist prior to setting the user quota.

Procedure 17.3. Assigning Quotas per User

  1. To assign the quota for a user, use the following command: 
    # edquota username
    Copy to Clipboard Toggle word wrap
    Replace username with the user to which you want to assign the quotas.
  2. To verify that the quota for the user has been set, use the following command: 
    # quota username
    Copy to Clipboard Toggle word wrap

Example 17.3. Assigning Quotas to a user

For example, if a quota is enabled in /etc/fstab for the /home partition (/dev/VolGroup00/LogVol02 in the following example) and the command edquota testuser is executed, the following is shown in the editor configured as the default for the system: 
Disk quotas for user testuser (uid 501):
		Filesystem                blocks     soft     hard    inodes   soft   hard
		/dev/VolGroup00/LogVol02  440436        0        0     37418      0      0
Copy to Clipboard Toggle word wrap

Note

The text editor defined by the EDITOR environment variable is used by edquota. To change the editor, set the EDITOR environment variable in your ~/.bash_profile file to the full path of the editor of your choice.
The first column is the name of the file system that has a quota enabled for it. The second column shows how many blocks the user is currently using. The next two columns are used to set soft and hard block limits for the user on the file system. The inodes column shows how many inodes the user is currently using. The last two columns are used to set the soft and hard inode limits for the user on the file system.
The hard block limit is the absolute maximum amount of disk space that a user or group can use. Once this limit is reached, no further disk space can be used.
The soft block limit defines the maximum amount of disk space that can be used. However, unlike the hard limit, the soft limit can be exceeded for a certain amount of time. That time is known as the grace period. The grace period can be expressed in seconds, minutes, hours, days, weeks, or months.
If any of the values are set to 0, that limit is not set. In the text editor, change the desired limits.

Example 17.4. Change Desired Limits

For example: 
Disk quotas for user testuser (uid 501):
Filesystem                blocks     soft     hard   inodes   soft   hard
/dev/VolGroup00/LogVol02  440436   500000   550000    37418      0      0
Copy to Clipboard Toggle word wrap
To verify that the quota for the user has been set, use the command: 
# quota testuser
Disk quotas for user username (uid 501):
   Filesystem  blocks   quota   limit   grace   files   quota   limit   grace
     /dev/sdb    1000*   1000    1000               0       0       0
Copy to Clipboard Toggle word wrap

17.1.5. Assigning Quotas per Group
Copy link

Quotas can also be assigned on a per-group basis.
Prerequisite
  • Group must exist prior to setting the group quota.

Procedure 17.4. Assigning Quotas per Group

  1. To set a group quota, use the following command: 
    # edquota -g groupname
    Copy to Clipboard Toggle word wrap
  2. To verify that the group quota is set, use the following command: 
    # Emptyquota -g groupname
    Copy to Clipboard Toggle word wrap

Example 17.5. Assigning quotas to group

For example, to set a group quota for the devel group, use the command: 
# edquota -g devel
Copy to Clipboard Toggle word wrap
This command displays the existing quota for the group in the text editor: 
Disk quotas for group devel (gid 505):
Filesystem                blocks    soft     hard    inodes    soft    hard
/dev/VolGroup00/LogVol02  440400       0        0     37418       0       0
Copy to Clipboard Toggle word wrap
Modify the limits, then save the file.
To verify that the group quota has been set, use the command: 
# quota -g devel
Copy to Clipboard Toggle word wrap

17.1.6. Setting the Grace Period for Soft Limits
Copy link

If a given quota has soft limits, you can edit the grace period (i.e. the amount of time a soft limit can be exceeded) with the following command: 
# edquota -t
Copy to Clipboard Toggle word wrap
This command works on quotas for inodes or blocks, for either users or groups.

Important

While other edquota commands operate on quotas for a particular user or group, the -t option operates on every file system with quotas enabled.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat