Home > Storage > PowerScale (Isilon) > Product Documentation > Storage (general) > Storage Quota Management and Provisioning with Dell PowerScale SmartQuotas > Default quota domains
A default quota domain does not account for any specific set of files but instead specifies a policy for new domains that match a specific trigger. In other words, default domains are configuration templates for actual domains. SmartQuotas uses the identity notations default-user, default-group, and default-directory to describe domains with default policies. For example, the domain default-user@/ifs/home becomes specific-user@/ifs/home for each specific user that is not otherwise defined. All enforcement on default-user are copied to specific-user when the specific-user allocates within the domain and the new inherited domain quota is a “linked quota”. There may be overlapping defaults (default-user@/ifs and default-user@/ifs/home may both be defined).
Default quota domains help drastically simplify quota management for large environments by providing a mechanism to define top-level template configurations from which many actual quotas are cloned, or linked. When a default quota domain is configured on a directory, any subdirectories created directly underneath the directory automatically inherit the quota limits specified in the parent domain. This mechanism streamlines the provisioning and management quotas for large enterprise environments. Furthermore, default directory quotas can co-exist with the user and/or group quotas and legacy default quotas.
Default directory quotas are available in OneFS 8.2 and later, in addition to the default user and group quotas available in earlier releases.
If the enforcements on a default domain change, SmartQuotas automatically propagates the changes to the linked quota domains. If a default quota domain is deleted, SmartQuotas deletes all children marked as inherited. An administrator may also choose to delete the default quota domain without deleting the children, but this will break inheritance on all inherited children.
A domain can be in one of three accounting states, as described in the following table:
Domain accounting state | Description |
Ready | A domain in the ready state is fully accounted. SmartQuotas displays “ready” domains in all interfaces and all enforcements apply to such domains. |
Accounting | A domain is placed in the accounting state when it is waiting on accounting updates. |
Deleting | After a request to delete a domain, SmartQuotas places the domain in the deleting state until the tear-down is complete. Domain removal might be a lengthy process. |
SmartQuotas displays accounting domains in all interfaces including usage data but indicates they are in the process of being “accounted.” SmartQuotas applies all enforcements to accounting domains, even when it might reject an allocation that would have proceeded if it had completed the QuotaScan.
Domains in the deleting state are hidden from all interfaces, and the top-level directory of a domain may be deleted while the domain is still in the deleting state (assuming that no domains are in a ready or accounting state, defined on the directory). No enforcements are applied for domains in the deleting state.
A quota scan is performed when the domain is in an accounting state. This can occur during quota creation to account for the new domain, if a quota has been set for the domain, and quota deletion to un-account the domain. A QuotaScan is required when creating a quota on a nonempty directory. If quotas are created upfront on an empty directory, no QuotaScan is necessary.
In addition, a QuotaScan job may be started from the WebUI or the command-line interface using the isi job command. Any path specified on the command line is treated as the root of a tree to be processed. This functionality is provided primarily as a means to rescan a directory or for maintenance reasons.