|-a||If supplied in place of any file system names, quotacheck will check all the file systems indicated in /etc/fstab to be read-write with disk quotas. By default only the types of quotas listed in /etc/fstab are checked.|
|-g||Only group quotas listed in /etc/fstab are to be checked.|
|Specifies the maximum number of concurrent file systems to check in parallel. If this option is omitted, or if maxrun is zero, parallel passes are run as per fsck(8).|
|-u||Only user quotas listed in /etc/fstab are to be checked.|
|-v||Report discrepancies between the calculated and recorded disk quotas and other additional diagnostic messages.|
Specifying both -g and -u is equivalent to the default. Parallel passes are run on the file systems required, using the pass numbers in /etc/fstab in an identical fashion to fsck(8).
Normally, quotacheck operates silently.
The quotacheck utility expects each file system to be checked to have a quota files named quota.user and quota.group which are located at the root of the associated file system. These defaults may be overridden in /etc/fstab. If a file is not present, quotacheck will create it. These files should be edited with the edquota(8) utility.
utility is normally run at boot time from the
The rc startup procedure is controlled by the
Note that to enable this functionality in
you also need to enable startup quota procedures
with the variable
The kernel must also be built with
.Cd options QUOTA .
The quotacheck utility accesses the raw device in calculating the actual disk usage for each user. Thus, the file systems checked should be quiescent while quotacheck is running.
quota.user at the file system root with user quotas quota.group at the file system root with group quotas /etc/fstab default file systems
The quotacheck utility appeared in BSD 4.2 .
The quota system will ignore UIDs or GIDs that would be negative when evaluated as a signed value. Typically those types of ids can appear in the file system from NFS mounts or archive files from other operating systems. Extremely large UIDs or GIDs will cause quotacheck to run for an unreasonable amount of time and also produce extremely large quota data files.
|January 25, 2007||QUOTACHECK (8)|