Separate TrueNAS dataset quotas from child-inclusive limits

Bottom line: Name the dataset population that a capacity setting should cover before entering a number. Keep quota limits, reserved space and alert thresholds as separate reviewed decisions.

Source fact: what the authority says

The TrueNAS 25.10 dataset reference allows a quota for only the selected dataset or for the dataset and its children. The quota fields use zero to disable quotas. Quota warning and critical alert percentages inherit from the parent by default and can be changed by clearing Inherit. The reference separately provides reserved-space fields for the dataset and for the dataset with its children.

What the source does not establish

This article addresses hierarchy and capacity-setting scope in the versioned reference. It does not equate a quota with a backup, establish an application growth forecast or prove that an alert reaches the responsible person.

Applicability questions

• Which exact parent and child datasets belong in the capacity limit?
• Is the requirement a maximum allowance, a space reservation or both?
• Which alert percentages are inherited and which should be explicitly selected?
• Who owns growth review for data outside the chosen subtree?

DSE recommendation: controlled next steps

The following steps are DSE recommendations based on the cited source.

DSE recommends drawing the relevant dataset tree and annotating which nodes belong inside the proposed limit. Put the selected dataset path beside the capacity value. Ask the data owner to review a sibling dataset explicitly so a familiar parent name does not hide an unintended accounting scope.

Write quota and reservation intentions in separate worksheet columns. Record the units and the reason for each value, including any deliberate zero. Do not enter zero as a placeholder for an undecided limit; resolve the capacity requirement before submitting the change.

Review warning and critical percentages alongside their inheritance state. If a parent setting is intended, identify the parent and record that decision. If a child needs its own thresholds, document why before clearing inheritance. Keep the notification recipient and response process in the separate alert-delivery review.

Prepare a small disposable parent-and-child arrangement for a proposed rehearsal. Give it an approved safe capacity budget and exclude operational data. Choose harmless writes at the parent and at one child so the reviewer can compare the intended scope without filling a production filesystem.

Verification and evidence

Proposed verification: inspect the effective quota, reservation and threshold settings for each named test dataset. Compare the recorded paths and inheritance state with the annotated tree. Write the planned small amount of harmless data separately at the parent and child, observing the capacity figures after each step.

Compare what was observed with the scope expected for the selected setting. If the result is unclear, stop and inspect the exact dataset and field rather than increasing a limit experimentally. Retain the units, hierarchy and observations together, and remove only the disposable rehearsal data through the agreed cleanup plan.

Official references

• TrueNAS — Datasets — official product documentation; confirm the installed release and configuration.

Source review completed October 29, 2026. Recheck the official documentation and deployment-specific applicability before a production change.