Sample quota entries

Explicit quota examples

The following list contains examples of explicit quotas:

jsmith user@/vol/rls 500M 10K
The user named jsmith can use 500 MB of disk space and 10,240 files in the rls volume.
jsmith,corp\jsmith,engineering\"john smith",
S-1-5-32-544 user@/vol/rls 500M 10K

This user, represented by four IDs, can use 500 MB of disk space and 10,240 files in the rls volume.
writers group@/vol/cad/proj1 150M
The writers group can use 150 MB of disk space and an unlimited number of files in the /vol/cad/proj1 qtree.
/vol/cad/proj1 tree 750M 75K
The proj1 qtree in the cad volume can use 750 MB of disk space and 76,800 files.

Tracking quota examples

The following list contains examples of tracking quotas:

root user@/vol/rls - -
Data ONTAP tracks but does not limit the amount of disk space and the number of files in the rls volume owned by root.
builtin\administrators user@/vol/rls - -
Data ONTAP tracks but does not limit the amount of disk space and the number of files in the rls volume owned by or created by members of BUILTIN\Administrators.
/vol/cad/proj1 tree - -
Data ONTAP tracks but does not limit the amount of disk space and the number of files for the proj1 qtree in the cad volume.

Default quota examples

The following list contains examples of default quotas:

* user@/vol/cad 50M 15K
Any user not explicitly listed in the quota file can use 50 MB of disk space and 15,360 files in the cad volume.
* group@/vol/cad 750M 85K
Any group not explicitly listed in the quota file can use 750 MB of disk space and 87,040 files in the cad volume.
* tree@vol/cad 75M
Any qtree in the cad volume that is not explicitly listed in the quota file can use 75 MB of disk space and an unlimited number of files.

Default tracking quota example

Default tracking quotas enable you to create default quotas that do not enforce any resource limits. This is helpful when you want to use the quota resize command when you modify your /etc/quotas file, but you do not want to apply resource limits with your default quotas. Default tracking quotas are created per-volume, as shown in the following example:

#Quota Target    type            disk  files  thold  sdisk  sfile

#------------    ----            ----  -----  -----  -----  -----

*                user@/vol/vol1   -      -

*                group@/vol/vol1  -      -

*                tree@/vol/vol1   -      -

Sample quota file and explanation

The following sample /etc/quotas file contains default quotas and explicit quotas:

#Quota Target type                disk  files  thold  sdisk  sfile

#------------ ----                ----  -----  -----  -----  -----

*             user@/vol/cad       50M   15K

*             group@/vol/cad      750M  85K

*             tree@/vol/cad       100M  75K

jdoe          user@/vol/cad/proj1 100M  75K

msmith        user@/vol/cad       75M   75K

msmith        user@/vol/cad/proj1 75M   75K

The following list explains the effects of these /etc/quotas entries:

Any user not otherwise mentioned in this file can use 50 MB of disk space and 15,360 files in the cad volume.
Any group not otherwise mentioned in this file can use 750 MB of disk space and 87,040 files in the cad volume.
Any qtree in the cad volume not otherwise mentioned in this file can use 100 MB of disk space and 76,800 files.
If a qtree is created in the cad volume (for example, a qtree named /vol/cad/proj2), Data ONTAP enforces a derived default user quota and a derived default group quota that have the same effect as these quota entries:
* user@/vol/cad/proj2 50M 15K

* group@/vol/cad/proj2 750M 85K
If a qtree is created in the cad volume (for example, a qtree named /vol/cad/proj2), Data ONTAP tracks the disk space and number of files owned by UID 0 and GID 0 in the /vol/cad/proj2 qtree. This is due to this quota file entry:
* tree@/vol/cad 100M 75K
A user named msmith can use 75 MB of disk space and 76,800 files in the cad volume because an explicit quota for this user exists in the /etc/quotas file, overriding the default limit of 50 MB of disk space and 15,360 files.
By giving jdoe and msmith 100 MB and 75 MB explicit quotas for the proj1 qtree, which has a tree quota of 100MB, that qtree becomes oversubscribed. This means that the qtree could run out of space before the user quotas are exhausted.
Quota oversubscription is supported; however, a warning is printed alerting you to the oversubscription.

How conflicting quotas are resolved

When more than one quota is in effect, the most restrictive quota is applied. Consider the following example /etc/quota file:

*                     tree@/vol/cad          100M      75K

jdoe                  user@/vol/cad/proj1    750M      75K

Because the jdoe user has a disk quota of 750 MB in the proj1 qtree, you might expect that to be the limit applied in that qtree. But the proj1 qtree has a tree quota of 100 MB, because of the first line in the quota file. So jdoe will not be able to write more than 100 MB to the qtree. If other users have already written to the proj1 qtree, the limit would be reached even sooner.

To remedy this situation, you can create an explicit tree quota for the proj1 qtree, as shown in this example:

*                    tree@/vol/cad           100M      75K

/vol/cad/proj1       tree                    800M      75K

jdoe                 user@/vol/cad/proj1     750M      75K

Now the jdoe user is no longer restricted by the default tree quota and can use the entire 750 MB of the user quota in the proj1 qtree.