quota.user(5) [freebsd man page]
QUOTA.USER(5) BSD File Formats Manual QUOTA.USER(5) NAME
quota.user, quota.group -- per file system quota database DESCRIPTION
Each file system with active quotas should contain a quota.user and quota.group file in the file system root. These files are created by quotacheck(8), and should be edited with edquota(8). It is possible to specify a different location and file name with the ``userquota'' and ``groupquota'' options in the fstab(5) file. The data files contain the following information: o Current block usage o Current number of files o Soft block limit o Soft file limit o Hard block limit o Hard file limit o Block grace time remaining if over the soft limit o File grace time remaining if over the soft limit See edquota(8) for an explanation on the various limits and grace periods. During normal quota operations the quotactl(2) interface is used to query or set quota information and the kernel will maintain the data files as needed. If quotas are disabled on a file system, but marked as having quotas enabled in fstab(5), then the quota data files will be used directly. The data files are stored as an array of ``struct dqblk'' structures, as defined in <ufs/ufs/quota.h>, and indexed by UID or GID. The data files will be written as a sparse file if possible. Data is only maintained for ids that have either non-zero usage or non-zero quota lim- its. If an attempt is made to access data for an id that would exist past the end of the current data file, a quota structure with all val- ues set to zero will be created, and the data file extended as needed. The quotacheck(8) utility will truncate the data files to the minimum size needed to store the highest id with either non-zero file usage or non-zero quota limits. The data record for id 0 has special meaning. If the ``dqb_btime'' or ``dbq_itime'' fields are non-zero, they are used to indicate the grace period on that file system for users who have exceeded their soft limit. These times can be set by edquota(8) with the -t flag. If no explicit grace period has been set with edquota(8), then the default value of 7 days will be used. The default values are defined by MAX_DQ_TIME and MAX_IQ_TIME in <ufs/ufs/quota.h>. SEE ALSO
quota(1), quotactl(2), fstab(5), edquota(8), quotacheck(8), quotaoff(8), quotaon(8), repquota(8) BSD
October 30, 2007 BSD
Check Out this Related Man Page
EDQUOTA(8) BSD System Manager's Manual EDQUOTA(8) NAME
edquota -- edit user quotas SYNOPSIS
edquota [-u] [-p proto-username] username ... edquota -g [-p proto-groupname] groupname ... edquota -t [-u] edquota -t -g DESCRIPTION
Edquota is a quota editor. By default, or if the -u flag is specified, one or more users may be specified on the command line. For each user a temporary file is created with an ASCII representation of the current disk quotas for that user. The list of filesystems with user quotas is determined by scanning the mounted filesystems for a .quota.ops.user file located at its root. An editor is invoked on the ASCII file. The editor invoked is vi(1) unless the environment variable EDITOR specifies otherwise. The quotas may then be modified, new quotas added, etc. Setting a quota to zero indicates that no quota should be imposed. Setting a hard limit to one indicates that no allocations should be permitted. Setting a soft limit to one with a hard limit of zero indicates that alloca- tions should be permitted on only a temporary basis (see -t below). The current usage information in the file is for informational purposes; only the hard and soft limits can be changed. On leaving the editor, edquota reads the temporary file and modifies the binary quota files to reflect the changes made. The binary quota file, .quota.user is stored at the root of the filesystem. The default filename and root location for the user quotas cannot be overridden. If the -p flag is specified, edquota will duplicate the quotas of the prototypical user specified for each user specified. This is the nor- mal mechanism used to initialize quotas for groups of users. If the -g flag is specified, edquota is invoked to edit the quotas of one or more groups specified on the command line. The list of filesys- tems with group quotas is determined by scanning the mounted filesystems for a .quota.ops.group file located at its root. Similarly, the binary quota file, .quota.group is stored at the root of the filesystem. The default filename and root location for group quotas cannot be overridden. The -p flag can be specified in conjunction with the -g flag to specify a prototypical group to be duplicated among the listed set of groups. 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 default grace period for a filesystem is specified in /usr/include/sys/quota.h. The -t flag can be used to change the grace period. By default, or when invoked with the -u flag, the grace period is set for each filesystem with a .quota.ops.user file located at its root. When invoked with the -g flag, the grace period is set for each filesystem with a .quota.ops.group file located at its root. The grace period may be specified in days, hours, minutes, or seconds. Setting a grace period to zero indicates that the default grace period should be imposed. Setting a grace period to one second indicates that no grace period should be granted. Only the super-user may edit quotas. FILES
Each of the following quota files is located at the root of the mounted filesystem. The mount option files are empty files whose existence indicates that quotas are to be enabled for that filesystem. The binary data files will be created by edquota, if they don't already exist. .quota.user data file containing user quotas .quota.group data file containing group quotas .quota.ops.user mount option file used to enable user quotas .quota.ops.group mount option file used to enable group quotas SEE ALSO
quota(1), quotactl(2), quotacheck(8), quotaon(8), repquota(8) DIAGNOSTICS
Various messages about inaccessible files; self-explanatory. BSD
June 2, 2019 BSD