Table of ContentsView in Frames

How you can use the quota report to see what quotas are in effect

Because of the various ways that quotas interact, more quotas are in effect than just the ones you have explicitly created. To see what quotas are in effect, you can view the quota report.

The following examples show quota reports for different types of quotas applied on a volume vol1, and a qtree q1 contained in that volume.

Example with no user quotas specified for the qtree

In this example, there is one qtree, q1, which is contained by the volume vol1. The administrator has created three quotas:
  • A default tree quota limit on vol1 of 400 MB
  • A default user quota limit on vol1 of 100 MB
  • An explicit user quota limit on vol1 of 200 MB for the user jsmith
The quotas file for these quotas looks similar to the following excerpt:
#Quota target type            disk files  thold sdisk  sfile
#-----------  ----            ---  -----  ----  -----  -----
*             tree@/vol/vol1  400M
*             user@/vol/vol1  100M
jsmith        user@/vol/vol1  200M
The quota report for these quotas looks similar to the following excerpt:
sys1> quota report
                                 K-Bytes             Files
Type       ID    Volume    Tree  Used      Limit     Used    Limit   Quota Specifier
----- -------- -------- -------- --------- --------- ------- ------- ---------------
tree         *     vol1        -         0    409600       0       - *
user         *     vol1        -         0    102400       0       - *
user    jsmith     vol1        -       112    204800       7       - jsmith
tree         1     vol1       q1         0    409600       6       - /vol/vol1/q1
user         *     vol1       q1         0    102400       0       - 
user    jsmith     vol1       q1         0    102400       5       -
user      root     vol1       q1         0         -       1       -
user      root     vol1        -         0         -       8       -

The first three lines of the quota report display the three quotas specified by the administrator. Since two of these quotas are default quotas, Data ONTAP automatically creates derived quotas.

The fourth line displays the tree quota that is derived from the default tree quota for every qtree in vol1 (in this example, only q1).

The fifth line displays the default user quota that is created for the qtree as a result of the existence of the default user quota on the volume and the qtree quota.

The sixth line displays the derived user quota that is created for jsmith on the qtree because there is a default user quota for the qtree (line 5) and the user jsmith owns files on that qtree. Note that the limit applied to the user jsmith in the qtree q1 is not determined by the explicit user quota limit (200 MB). This is because the explicit user quota limit is on the volume, so it does not affect limits for the qtree. Instead, the derived user quota limit for the qtree is determined by the default user quota for the qtree (100 MB).

The last two lines display more user quotas that are derived from the default user quotas on the volume and on the qtree. A derived user quota was created for the root user on both the volume and the qtree because the root user owned files on both the volume and the qtree. Since the root user gets special treatment in terms of quotas, its derived quotas are tracking quotas only.

Example with user quotas specified for the qtree

This example is similar to the previous one, except that the administrator has added two quotas on the qtree.

There is still one volume, vol1, and one qtree, q1. The administrator has created the following quotas:
  • A default tree quota limit on vol1 of 400 MB
  • A default user quota limit on vol1 of 100 MB
  • An explicit user quota limit on vol1 for the user jsmith of 200 MB
  • A default user quota limit on qtree q1 of 50 MB
  • An explicit user quota limit on qtree q1 for the user jsmith of 75 MB
The quotas file for these quotas looks like this:
#Quota target type             disk files  thold sdisk  sfile
#-----------  ----             ---  -----  ----  -----  -----
*             tree@/vol/vol1   400M
*             user@/vol/vol1   100M
jsmith        user@/vol/vol1   200M
*             user@/vol/vol1/q1 50M
jsmith        user@/vol/vol1/q1 75M
The quota report for these quotas looks like this:
sys1> quota report
                                 K-Bytes             Files
Type       ID    Volume    Tree  Used      Limit     Used    Limit   Quota Specifier
----- -------- -------- -------- --------- --------- ------- ------- ---------------
tree         *     vol1        -         0    409600       0       - *
user         *     vol1        -         0    102400       0       - *
user    jsmith     vol1        -       112    204800       7       - jsmith
user         *     vol1       q1         0     51200       0       - *
user    jsmith     vol1       q1         0     76800       5       - jsmith
tree         1     vol1       q1         0    409600       6       - /vol/vol1/q1
user      root     vol1        -         0         -       2       -
user      root     vol1       q1         0         -       1       -

The first five lines of the quota report display the five quotas created by the administrator. Since some of these quotas are default quotas, Data ONTAP automatically creates derived quotas.

The sixth line displays the tree quota that is derived from the default tree quota for every qtree in vol1 (in this example, only q1).

The last two lines display the user quotas that are derived from the default user quotas on the volume and on the qtree. A derived user quota was created for the root user on both the volume and the qtree because the root user owned files on both the volume and the qtree. Since the root user gets special treatment in terms of quotas, its derived quotas are tracking quotas only.

No other default quotas or derived quotas were created for the following reasons:
  • A derived user quota was not created for the jsmith user even though the user owns files on both the volume and the qtree because the user already has explicit quotas at both levels.
  • No derived user quotas were created for other users because no other users own files on either the volume or the qtree.
  • The default user quota on the volume did not create a default user quota on the qtree because the qtree already had a default user quota.