NAME<\/a> quotacheck \u2212 scan a filesystem for disk usage, create, check and repair quota files<\/p>\n quotacheck<\/b> [ \u2212gubcfinvdMmR<\/b> ] [ \u2212F<\/b> quota-format<\/i> ] \u2212a<\/b> | filesystem<\/i><\/p>\n quotacheck<\/b><\/i> examines each filesystem, builds a table of current disk usage, and compares this table against that recorded in the disk quota file for the filesystem (this step is omitted if option -c<\/b> is specified). If any inconsistencies are detected, both the quota file and the current system copy of the incorrect quotas are updated (the latter only occurs if an active filesystem is checked which is not advised). By default, only user quotas are checked. quotacheck<\/b> expects each filesystem to be checked to have quota files named [a]quota.user<\/i> and [a]quota.group<\/i> located at the root of the associated filesystem. If a file is not present, quotacheck<\/b> will create it.<\/p>\n If the quota file is corrupted, quotacheck<\/b> tries to save as much data as possible. Rescuing data may need user intervention. With no additional options quotacheck<\/b> will simply exit in such a situation. When in interactive mode (option -i<\/b>) , the user is asked for advice. Advice can also be provided from command line (see option -n<\/b>) , which is useful when quotacheck<\/b> is run automatically (ie. from script) and failure is unacceptable.<\/p>\n quotacheck<\/b> should be run each time the system boots and mounts non-valid filesystems. This is most likely to happen after a system crash.<\/p>\n It is strongly recommended to run quotacheck<\/b> with quotas turned off for the filesystem. Otherwise, possible damage or loss to data in the quota files can result. It is also unwise to run quotacheck<\/b> on a live filesystem as actual usage may change during the scan. To prevent this, quotacheck<\/b> tries to remount the filesystem read-only before starting the scan. After the scan is done it remounts the filesystem read-write. You can disable this with option \u2212m<\/b>. You can also make quotacheck<\/b> ignore the failure to remount the filesystem read-only with option \u2212M<\/b>.<\/p>\n -b, –backup<\/b><\/p>\n Forces quotacheck<\/b> to make backups of the quota file before writing the new data.<\/p>\n -v, –verbose<\/b><\/p>\n quotacheck<\/b> reports its operation as it progresses. Normally it operates silently. If the option is specified twice, also the current directory is printed (note that printing can slow down the scan measurably).<\/p>\n -d, –debug<\/b><\/p>\n Enable debugging mode. It will result in a lot of information which can be used in debugging the program. The output is very verbose and the scan will be slow.<\/p>\n -u, –user<\/b><\/p>\n Only user quotas listed in \/etc\/mtab<\/i> or on the filesystems specified are to be checked. This is the default action.<\/p>\n -g, –group<\/b><\/p>\n Only group quotas listed in \/etc\/mtab<\/i> or on the filesystems specified are to be checked.<\/p>\n -c, –create-files<\/b><\/p>\n Don\u2019t read existing quota files. Just perform a new scan and save it to disk. quotacheck<\/b> also skips scanning of old quota files when they are not found.<\/p>\n -f, –force<\/b><\/p>\n Forces checking and writing of new quota files on filesystems with quotas enabled. This is not recommended as the created quota files may be out of sync.<\/p>\n -M, –try-remount<\/b><\/p>\n This flag forces checking of filesystem in read-write mode if a remount fails. Do this only when you are sure no process will write to a filesystem while scanning.<\/p>\n -m, –no-remount<\/b><\/p>\n Don\u2019t try to remount filesystem read-only. See comment with option \u2212M<\/b>.<\/p>\n -i, –interactive<\/b><\/p>\n Interactive mode. By default quotacheck<\/b> exits when it finds an error. In interactive mode user is asked for input instead. See option \u2212n<\/b>.<\/p>\n -n, –use-first-dquot<\/b><\/p>\n If the quota files become corrupted, it is possible for duplicate entries for a single user or group ID to exist. Normally in this case, quotacheck<\/b> exits or asks user for input. When this option is set, the first entry found is always used (this option works in interactive mode too).<\/p>\n -F, –format=<\/b>format-name<\/i><\/p>\n Check and fix quota files of specified format (ie. don\u2019t perform format auto-detection). This is recommended as detection might not work well on corrupted quota files. Possible format names are: vfsold<\/b> Original quota format with 16-bit UIDs \/ GIDs, vfsv0<\/b> Quota format with 32-bit UIDs \/ GIDs, 64-bit space usage, 32-bit inode usage and limits, vfsv1<\/b> Quota format with 64-bit quota limits and usage, rpc<\/b> (quota over NFS), xfs<\/b> (quota on XFS filesystem)<\/p>\n -a, –all<\/b><\/p>\n Check all mounted non-NFS filesystems in \/etc\/mtab<\/b><\/p>\n -R, –exclude-root<\/b><\/p>\n When used together with the \u2212a<\/b> option, all filesystems except for the root filesystem are checked for quotas.<\/p>\n quotacheck<\/b> should only be run by super-user. Non-privileged users are presumably not allowed to read all the directories on the given filesystem.<\/p>\n quota<\/b>(1), quotactl<\/b>(2), fstab<\/b>(5), quotaon<\/b>(8), repquota<\/b>(8), convertquota<\/b>(8), setquota<\/b>(8), edquota<\/b>(8), fsck<\/b>(8), efsck<\/b>(8), e2fsck<\/b>(8), xfsck<\/b>(8)<\/p>\n aquota.user or aquota.group<\/b><\/p>\n located at filesystem root with quotas (version 2 quota, non-XFS filesystems)<\/p>\n quota.user or quota.group<\/b><\/p>\n located at filesystem root with quotas (version 1 quota, non-XFS filesystems)<\/p>\n
SYNOPSIS<\/a>
DESCRIPTION<\/a>
OPTIONS<\/a>
NOTE<\/a>
SEE ALSO<\/a>
FILES<\/a>
AUTHOR<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
OPTIONS <\/a> <\/h2>\n
NOTE <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n
FILES <\/a> <\/h2>\n