LEARN. PRACTICE. GROW.Concept and mechanism
Available NAS capacity does not mean headroom for every consumer. A quota can limit bytes or file count depending on implementation. In the ONTAP examples, hard limits prevent operations exceeding the limit, while soft limits and thresholds generate warnings without blocking those operations. Do not generalize this behavior to products with different rules. In an example with an eighty-GiB soft limit and a hundred-GiB hard limit, moving from seventy-nine to eighty-one GiB is not blocked by the soft limit, assuming no other limit is reached. The warning should trigger growth and retention analysis before an actual failure.
Guided application
Many small files can reach a hard files limit despite spare GiB. Investigate population, consumption, and content still needing preservation before cleanup. For performance, low throughput does not establish light load: metadata creation and lookup can dominate elapsed time. mountstats provides per-mount operation observations; nfsstat distinguishes client and server sides. Also confirm the window: the first mountstats iostat report covers time since mounting, while subsequent reports cover intervals. Comparing these values as though they represent the same window can invent a regression. During a fictional incident, correlate operations, latency, and quota with the affected batch instead of relying only on the MiB/s graph.
A reached hard files limit can deny another file even with substantial free space.
Common pitfalls
GiB as every quota; soft as universal blocking; cumulative sample as interval; few bytes as little work.
Related topics: Shares and mounting · Identity and permissions · Security and write acknowledgement
Identify the constrained resource and compare measurements with the same scope.
Reference: ONTAP hard, soft and threshold quotas · DR NAS 2026-09; selected Linux NFS, Samba, Windows SMB and ONTAP behavior