GPFS: Administration and Programming Reference - IRA Home

During the normal operation of file systems with quotas enabled (not running mmcheckquota online), the
usage data reflects the actual usage of the blocks and inodes in the sense that if you delete files you
should see the usage amount decrease. The in doubt value does not reflect how much the user has used
already, it is just the amount of quotas that the quota server has assigned to its clients. The quota server
does not know whether the assigned amount has been used or not. The only situation where the in doubt
value is important to the user is when the sum of the usage and the in doubt value is greater than the
user’s quota hard limit. In this case, the user is not allowed to allocate more blocks or inodes unless he
brings the usage down.
For example, to check quotas for the file system fs1 and report differences between calculated and
recorded disk quotas, enter:
mmcheckquota -v fs1
The information displayed shows that the quota information for USR7 was corrected. Due to a system
failure, this information was lost at the server, which recorded 0 subblocks and 0 files. The current usage
data counted is 96 subblocks and 3 files. This is used to update the quota:
/dev/fs1: quota-check found following differences:
USR7: 96 subblocks counted (was 0); 3 inodes counted (was 0)
See the “mmcheckquota Command” on page 98 for complete usage information.
Listing quotas
The mmlsquota command displays the file system quota limits, default quota limits, and current usage
information. GPFS quota management takes replication into account when reporting on and determining if
quota limits have been exceeded for both block and file usage. In a file system that has either type of
replication set to a value of two, the values reported on by both the mmlsquota command and the
mmrepquota command and the values used to determine if quota limits have been exceeded will be
double the value reported by the ls command. When issuing the mmlsquota command on a mounted file
system, negative in doubt values may be reported if the quota server processes a combination of
up-to-date and back-level information. This is a transient situation and may be ignored.
Specify the quota information for one user, group of users, or fileset with the mmlsquota command. If
neither -g , nor -u, nor -j is specified, quota data is displayed for the user who entered the command.
For example, to display default quota information for users of all the file systems in the cluster, enter:
mmlsquota -d -u
Information similar to this is returned:
Default Block Limits | Default File Limits
Filesystem type quota limit | quota limit Remarks
fs1 USR no default limits
This output shows for file system fs1 a default quota limit of 10240K for users has been established. For
file systems fs2 and fs3 no default quotas for users has been established.
If you issue the mmlsquota command with the -e option, the quota system collects updated information
from all nodes before returning output. If the node to which in-doubt space was allocated should fail before
updating the quota system about its actual usage, this space might be lost. Should the amount of space in
doubt approach a significant percentage of the quota, run the mmcheckquota command to account for
the lost space.
To collect and display updated quota information about a group named blueteam, specify the -g and -e
options:
mmlsquota -g blueteam -e
40 GPFS: Administration and Programming Reference