Disk quota

This article covers the installation and setup of disk quota.

From Wikipedia:

"A disk quota is a limit set by a system administrator that restricts certain aspects of file system usage on modern operating systems. The function of setting quotas to disks is to allocate limited disk-space in a reasonable way."

Installation

Install the quota-tools package.

Configuration

Set up the filesystem

Edit fstab to enable the quota mount option(s) on selected file systems, e.g.:

/etc/fstab
/dev/sda3 /home ext4 defaults''',usrquota''' 0 2

To additionally enable the group quota mount option:

/etc/fstab
/dev/sda3 /home ext4 defaults''',usrquota,grpquota''' 0 2

If supported by the kernel and file system it is recommended to use journaled quota instead:

/etc/fstab
/dev/sda3 /home ext4 defaults''',usrjquota=aquota.user,jqfmt=vfsv1''' 0 2

Append grpjquota=aquota.group to enable group quota.

Remount the partition to apply the change:

# mount -vo remount /home

Create quota index

To create the quota index for /home:

# quotacheck -cum /home

Append the -g parameter to also create a group index.

To enable disk quotas for the desired file system:

# quotaon -v /home

To disable disk quotas for the file system:

# quotaoff -v /home

Usage

Enable quota for user/group

Tip:
  • To find out how many 1 kilobyte blocks are there for a partition use $ df.
  • You may use a online bytes converter to calculate the correct amount of blocks .
  • The command # setquota may be used as an alternative of # edquota .
Note: Block size is statically set to 1k regardless of filesystem block size .

Quotas are configured using edquota (as the root user) that will be opened in the default configured text editor:

blocks
Indicates number of 1k blocks currently used by the user/group.
soft
Indicates max number of blocks for the user/group before a warning is issued and grace period countdown begins. If set to "0" (zero) then no limit is enforced.
hard
Indicates max number of blocks for the user/group can use. If maximum amount has been reached, no further disk space can be used. If set to "0" (zero) then no limit is enforced.
inodes
Indicates the current inodes amount used by the user/group.
soft
Indicates the soft inode limit for the user/group.
hard
Indicates the hard inode limit for the user/group.

Consider the following configuration for ftpuser1:

In this case if ftpuser1 uses over 976MB of space a warning will be issued. If the hard limit of 1GB has been reached the user will be unable to write any more data.

See #Specify a grace period to give users a specific amount of time to reduce storage usage when they hit their soft limit.

Warning: The hard limit applies to all files written by and for the respective user/group, including temporary files by started applications, which may crash at this point.

Specify a grace period

To give current users some time to reduce their file usage, a grace period can be configured. This specifies the allowed time a user/group can exceed their soft limit and while under their hard limit:

The grace period can be set in seconds, minutes, hours, days, weeks or months.

Reports

Shows all configured quotas:

# repquota -a

Shows quotas on a specific partition:

# repquota /home

Show quotas that apply to a user/user group:

# quota -u user
# quota -g group

To one or several users

To copy quota settings from to user2:

# edquota -p user1 user2

To copy quota settings to several other users, append ...

To groups

To copy quota settings from group1 to :

# edquota -g -p group1 group2

To all users

The idea is to modify the quota settings for one user and copy the setting to all other users. Set the quota for and apply the quota to users with a UID greater than 999:

# edquota -p user1 $(awk -F: '$3 > 999 {print $1}' /etc/passwd)

Tips and tricks

Quota warnings

The command can be used to warn the users about their quota. Configuration is available in .

Stats

The command can be used to give more information about the current quota usage:

gollark: Technologies have a lot of prerequisites.
gollark: They wouldn't just use worse technology for no particular reason, mostly.
gollark: The people in the past *were actually quite smart*.
gollark: Well, DRAM wasn't used for most of computing history.
gollark: Unfortunately for you, they would be too bad for you to do interesting stuff with for several decades.

See also

This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.