Release notes
The requested article is not available. Either it doesn't apply to this version of the product or the relevant information is organized differently in this version of the docs. You can search, browse, or go back to the other version.
Why enforced quotas differ from configured quotas
Contributors
Suggest changes
-
PDF of this doc site
-
Cluster administration
-
Volume administration
-
Logical storage management with the CLI
-
-
NAS storage management
-
Configure NFS with the CLI
-
Manage NFS with the CLI
-
Manage SMB with the CLI
-
Manage file access using SMB
-
-
-
Security and data encryption
-
Data protection and disaster recovery
-
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
Enforced quotas differ from configured quotas because derived quotas are enforced without being configured but configured quotas are enforced only after they are successfully initialized. Understanding these differences can help you compare the enforced quotas that are shown in quota reports to the quotas that you configured.
Enforced quotas, which appear in quota reports, might differ from the configured quota rules for the following reasons:
-
Derived quotas are enforced without being configured as quota rules. ONTAP creates derived quotas automatically in response to default quotas.
-
Quotas might not have been reinitialized on a volume after quota rules were configured.
-
Errors might have occurred when quotas were initialized on a volume.
