How quotas are activated overview

Contributors

New quotas and changes to quotas do not take effect until they are activated. Knowing how quota activation works can help you manage your quotas less disruptively.

You can activate quotas at the volume level.

Your quotas file does not need to be free of all errors to activate quotas. Invalid entries are reported and skipped. If the quotas file contains any valid entries, the quotas are activated.

Quotas are activated either by initializing (turning them on) or by resizing. Turning off quotas and turning them on again is called reinitializing.

The length of the activation process and its impact on quota enforcement depends on the type of activation:

  • The initialization process involves two parts: a quota on job and a quota scan of the volume’s entire file system. The scan begins after the quota on job completes successfully. The quota scan can take some time; the more files that the volume has, the longer it takes. Until the scan is finished, quota activation is not complete and quotas are not enforced.

  • The resize process involves only a quota resize job. Because it does not involve a quota scan, resizing takes less time than a quota initialization. During a resize process, quotas are enforced.

By default, the quota on and quota resize jobs run in the background, which permits you to use other commands at the same time.

Errors and warnings from the activation process are sent to the event management system. If you use the -foreground parameter with the volume quota on or volume quota resize commands, the command does not return until the job is complete; this is useful if you are reinitializing from a script. To display errors and warnings later, you can use the volume quota show command with the -instance parameter.

Quota activation persists across halts and reboots. The process of quota activation does not affect the availability of the storage system data.