- Do not exceed 500,000 quotas per cluster in OneFS 8.2 and 20,000 quotas per cluster in earlier releases.
- SmartQuotas schedule notification rules are limited to 20,000.
- In OneFS versions earlier than OneFS 8.2, SmartQuotas only reports the true quota container size for directory quotas (user and group quotas report the entire file system size). Beginning with OneFS 8.2, this functionality is extended to user and group quotas.
- NFS quota support allows customers to view quota soft and hard limits using UNIX and Linux-based quota tools (rpc.quotad protocol).
- With CloudPools data, the quota is calculated based on the size of the data local to the cluster. For example, for a 100 MB file tiered to a cloud provider, SmartQuotas would calculate just the size of the local stub file (8 K).
- SmartQuotas reports the logical capacity of the files, whether they are deduplicated or not.
- The QuotaScan job runs after the creation of a quota, but not after a change. However, it does run on a schedule and incorporates any changes then.
- If two quotas are created on the same directory—for example, an accounting quota without snapshots and a hard quota with snapshots—the quota without snapshot data overrules the limit from the quota with snapshot data.
- SmartQuotas also provide a low impact way to provide directory file count reports.
- Configuration changes for linked quotas must be made on the parent quota that the linked quota is inheriting from. Changes to the parent quota are propagated to all children. To override configuration from the parent quota, you must first unlink the quota.
- If a quota type uses the accounting-only option, enforcement limits cannot be used for that quota.
- Cloned and deduplicated files are treated as ordinary files by quotas. If the quota includes data-protection overhead, the data-protection overhead for shared data is not included in the usage calculation.
- Moving quota directories across quota domains is not supported.
- You can edit or delete a quota report only when the quota is not linked to a default quota.
- A quota can only be unlinked when it is linked to a default quota. Configuration changes for linked quotas must be made on the parent (default) quota that the linked quota is inheriting from. Changes to the parent quota are propagated to all children. If you want to override configuration from the parent quota, you must first unlink the quota.
- Disabling all quota notifications also disables all system notification behavior. Use the —clear options to remove specific quota notification rules and fall back to the system default.
- With support for multiple email recipients for notifications and alerts, the maximum supported size of the email address list (comma-separated) is 1,024 characters. Multiemail notifications can be configured with the following CLI syntax:
# isi quota notifications create </ifs/quota> directory advisory exceeded -–action-email-address=user1@mail.com,user2@mail.com,user3@mail.com -–holdoff=0
- Quota containers compartmentalize /ifs, so that a directory with a container appears as its own separate file system slice. To configure a directory quota with a 4 TB container on /ifs/data/container1, you could use the following CLI command:
# isi quota quotas create /ifs/data/container1 directory --hard-threshold 4T --container true
- Only soft or advisory limits can be defined as a percentage of a hard limit. Defining the same type of limit with both percent-based and absolute is not permitted in a single request.
- While OneFS 8.2 and later versions support an overall quota limit of up to 500,000, support for schedule notification rules is still limited to 20,000.