edquota is a quota editor. One or more users, groups, or projects
may be specified on the command line. If a number is given in the
place of user/group/project name it is treated as an UID/GID/Project
ID. For each user, group, or project a temporary file is created with
an ASCII representation of the current disk quotas for that user,
group, or project and an editor is then invoked on the file. The
quotas may then be modified, new quotas added, etc. Setting a quota
to zero indicates that no quota should be imposed.
Block usage and limits are reported and interpreted as multiples of
kibibyte (1024 bytes) blocks by default. Symbols K, M, G, and T can
be appended to numeric value to express kibibytes, mebibytes,
gibibytes, and tebibytes.
Inode usage and limits are interpreted literally. Symbols k, m, g,
and t can be appended to numeric value to express multiples of 10^3,
10^6, 10^9, and 10^12 inodes.
Users are permitted to exceed their soft limits for a grace period
that may be specified per filesystem. Once the grace period has
expired, the soft limit is enforced as a hard limit.
The current usage information in the file is for informational
purposes; only the hard and soft limits can be changed.
Upon leaving the editor, edquota reads the temporary file and
modifies the binary quota files to reflect the changes made.
The editor invoked is vi(1) unless either the EDITOR or the VISUAL
environment variable specifies otherwise.
Only the super-user may edit quotas.
Edit also non-local quota use rpc.rquotad on remote server to
set quota. This option is available only if quota tools were
compiled with enabled support for setting quotas over RPC.
The -n option is equivalent, and is maintained for backward
Currently, pathnames of NFSv4 mountpoints are sent without
leading slash in the path. rpc.rquotad uses this to recognize
NFSv4 mounts and properly prepend pseudoroot of NFS filesystem
to the path. If you specify this option, edquota will always
send paths with a leading slash. This can be useful for legacy
reasons but be aware that quota over RPC will stop working if
you are using new rpc.rquotad.
Edit the user quota. This is the default.
Edit the group quota.
Edit the project quota.
Duplicate the quotas of the prototypical user specified for
each user specified. This is the normal mechanism used to
initialize quotas for groups of users.
Always try to translate user / group name to uid / gid even if
the name is composed of digits only.
Edit quota for specified format (ie. don't perform format
autodetection). Possible format names are: vfsold Original
quota format with 16-bit UIDs / GIDs, vfsv0 Quota format with
32-bit UIDs / GIDs, 64-bit space usage, 32-bit inode usage and
limits, vfsv1 Quota format with 64-bit quota limits and usage,
rpc (quota over NFS), xfs (quota on XFS filesystem)
-f, --filesystem filesystem
Perform specified operations only for given filesystem
(default is to perform operations for all filesystems with
Edit the soft time limits for each filesystem. In old quota
format if the time limits are zero, the default time limits in
<linux/quota.h> are used. In new quota format time limits must
be specified (there is no default value set in kernel). Time
units of 'seconds', 'minutes', 'hours', and 'days' are
understood. Time limits are printed in the greatest possible
time unit such that the value is greater than or equal to one.
Edit time for the user/group/project when softlimit is
enforced. Possible values are 'unset' or number and unit.
Units are the same as in -t option.
This page is part of the quota (Linux Diskquota Tools) project.
Information about the project can be found at [unknown -- if you
know, please contact email@example.com] It is not known how to
report bugs for this man page; if you know, please send a mail to
firstname.lastname@example.org. This page was obtained from the project's
upstream Git repository
2017-03-13. If you discover any rendering problems in this HTML ver‐
sion of the page, or you believe there is a better or more up-to-date
source for the page, or you have corrections or improvements to the
information in this COLOPHON (which is not part of the original man‐
ual page), send a mail to email@example.com