mmedquota - Sets quota limits.
Synopsis
mmedquota {-u [-p ProtoUser] User... |
-g [-p ProtoGroup] Group... |
-d {-u User... | -g Group...} |
-t {-u | -g}}
Description
The mmedquota command serves two different purposes:
mmedquota displays the current values for these limits, if any, and prompts you to enter new values using your default editor:
Displayed in KB, but may be specified using k, K, m, or M. If no suffix is provided, the number is assumed to be in bytes.
Displayed in KB, but may be specified using k, K, m, or M. If no suffix is provided, the number is assumed to be in bytes.
The mmedquota command waits for the edit window to be closed before checking and applying new values. If an invalid entry is made, you must reissue the command and enter the correct values.
You can also use the mmedquota command to change the file system-specific grace periods for block and file usage if the default of one week is unsatisfactory. The grace period is the time during which users can exceed the soft limit. If the user or group does not reduce usage below the soft limit before the grace period expires, the soft limit becomes the new hard limit.
When setting quota limits for a file system, replication within the file system should be considered. 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.
The EDITOR environment variable must contain a complete path name, for example:
export EDITOR=/usr/bin/vi
Parameters
Options
When invoked with the -u option, ProtoUser limits are automatically applied to the specified User or space-delimited list of users.
When invoked with the -g option, ProtoGroup limits are automatically applied to the specified Group or space-delimited list of groups.
You can specify any user as a ProtoUser for another User, or any group as a ProtoGroup for another Group.
Exit status
Security
You must have root authority to run the mmedquota command.
GPFS must be running on the node from which the mmedquota command is issued.
In an SP environment, verify the authentication method set for SP security services:
For further information, see the latest IBM Parallel System Support Programs for AIX: Administration Guide, IBM Parallel System Support Programs for AIX: Command and Technical Reference, and RS/6000: Planning Volume 2, Control Workstation and Software Environment manuals at www.rs6000.ibm.com/resource/aix_resource/sp_books/pssp. Search for information on sysctl.
Examples
mmedquota -u paulThe system displays information in your default editor similar to:
*** Edit quota limits for USR paul: NOTE: block limits will be rounded up to the next multiple of the block size. gpfs0: blocks in use: 864K, limits (soft = 2500 , hard = 10M) inodes in use: 9, limits (soft = 100, hard = 1000)
mmedquota -d -g blueteamTo verify the change, enter:
mmrepquota -q fs1The system displays information similar to:
fs1: USR quota is on; default quota is on fs1: GRP quota is on; default quota is on
mmedquota -t -uThe system displays information in your default editor similar to:
*** Edit grace times: Time units may be : days, hours, minutes, or seconds Grace period before enforcing soft limits for USRs: gpfs0: block grace period: 7 days, file grace period: 7 days
See also
Location
/usr/lpp/mmfs/bin