Reinitializing quotas after making extensive changes

When you make extensive changes to existing quotas; for example, by adding or deleting quotas for targets that have no enforced quotas— you must make the changes and re-initialize quotas on all affected volumes.

1. Use the vserver show command with the -instance parameter to determine the name of the policy that is currently assigned to the SVM.
2. Modify quota rules by performing any of the following actions:

   If you want to...	Then...
   Create new quota rules	Use the volume quota policy rule create command
   Modify the settings of existing quota rules	Use the volume quota policy rule modify command
   Delete existing quota rules	Use the volume quota policy rule delete command

3. Use the volume quota policy rule show command to check that the quota rules are configured correctly.
4. Re-initialize quotas on each volume where you changed quotas by turning quotas off and then turning quotas on for those volumes.
   1. Use the volume quota off command on each affected volume to deactivate quotas on that volume.
   2. Use the volume quota on command on each affected volume to activate quotas on that volume.

      Note

      You must ensure that you wait for about five minutes before reactivating the quotas on each affected volume, as attempting to activate them almost immediately after running the volume quota off command might result in errors.

      Alternatively, you can run the commands to re-initialize the quotas for a volume from the node that contains the particular volume.

      You can monitor the initialization process in either of the following ways:

      • When you use the volume quota on command, you can add the -foreground parameter to run the quota on job in the foreground. (By default, the job runs in the background.)

        When the job runs in the background, you can monitor its progress by using the job show command.

      • You can use the volume quota show command to monitor the status of the quota initialization.

5. Use the volume quota show -instance command to check for initialization errors, such as quota rules that failed to initialize.
6. Use the volume quota report command to display a quota report so that you can ensure the enforced quotas match your expectations.