A short example quotas file, together with explanations, can help you to understand the different types of quota entries and how they affect your quotas.
The following sample quotas file contains both default and explicit quotas:
#Quota Target type disk files thold sdisk sfile
#------------ ---- ---- ----- ----- ----- -----
* user@/vol/vol1 50M 15K
* group@/vol/vol1 750M 85K
* tree@/vol/vol1 100M 75K
jdoe user@/vol/vol1/proj1 100M 75K
msmith user@/vol/vol1 75M 75K
msmith user@/vol/vol1/proj1 75M 75K
This quotas file has the following effects:
- Any user not otherwise mentioned in this file can use 50 MB of disk space and 15,360 files in the vol1 volume.
- Any group not otherwise mentioned in this file can use 750 MB of disk space and 87,040 files in the vol1 volume.
- Any qtree in the vol1 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 vol1 volume (for example, a qtree named /vol/vol1/proj2), Data ONTAP enforces a derived default user quota and a derived default group quota that have the same effect as the following quota entries:
* user@/vol/vol1/proj2 50M 15K
* group@/vol/vol1/proj2 750M 85K
- If a qtree is created in the vol1 volume (for example, a qtree named /vol/vol1/proj2), Data ONTAP tracks the disk space and number of files owned by UID 0 and GID 0 in the /vol/vol1/proj2 qtree. This is due to the following quotas file entry:
* tree@/vol/vol1 100M 75K
- A user named msmith can use 75 MB of disk space and 76,800 files in the vol1 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.
Note: Quota oversubscription is supported; however, a warning is printed alerting you to the oversubscription.