Section: Maintenance Commands (8)
Updated: Fri Jul 20 2001
Return to Main Contents
quotacheck - scan a filesystem for disk usage, create, check and repair quota files
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 ommitted if option
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.
expects each filesystem to be checked to have quota files named
located at the root of the associated filesystem. If a file is not
will create it.
If the quota file is corrupted,
tries to save as much data as possible. Rescuing data may need user
intervention. With no additional options
will simply exit in such a situation. When in interactive mode (option
, the user is asked for advice. Advice can also be provided from command
line (see option
, which is useful when
is run automatically (ie. from script) and failure is unacceptable.
should be run each time the system boots and mounts non-valid filesystems.
This is most likely to happen after a system crash.
It is strongly recommended to run
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
on a live filesystem as actual usage may change during the scan. To
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
You can also make
ignore the failure to remount the filesystem read-only with option
to make backups of the quota file before writing the new data.
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).
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.
Only user quotas listed in
or on the filesystems specified are to be checked. This is the default action.
Only group quotas listed in
or on the filesystems specified are to be checked.
Don't read existing quota files. Just perform a new scan and save it to disk.
also skips scanning of old quota files when they are not found.
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.
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.
Don't try to remount filesystem read-only. See comment with option
Interactive mode. By default
exits when it finds an error. In interactive mode user is asked for
input instead. See option
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,
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).
- -F format-name
Check and fix quota files of specified format (ie. don't perform format
auto-detection). This is recommended as detection might not work well on
corrupted quota files. Possible format names are:
(version 1 quota),
(version 2 quota),
(quota over NFS),
(quota on XFS filesystem)
Check all mounted non-NFS filesystems in
When used together with the
option, all filesystems except for the root filesystem are checked for
should only be run by super-user. Non-privileged users are presumably
not allowed to read all the directories on the given filesystem.
- aquota.user or aquota.group
located at filesystem root with quotas (version 2 quota, non-XFS
- quota.user or quota.group
located at filesystem root with quotas (version 1 quota, non-XFS
names and locations of mounted filesystems
Jan Kara <email@example.com>
Based on old
Edvard Tuinder <firstname.lastname@example.org>
Marco van Wieringen <email@example.com>
- SEE ALSO
linux.jgfs.net manual pages