Quota size differs between storage and host due to snapshot spill
Applies to
- ONTAP 9
- Quota
Issue
- Quota allocated size differs suddenly from storage end to host end
- Quota re-initialization also does not help in resolving the issue
Example :
Quota allocated space from storage end is 2.1TB, however on user end it displays limit as 1.5TB
Vserver : svm02
Volume : vol1
::*> volume show-space vol1
Feature Used Used%
-------------------------------- ---------- ------
User Data 474.7GB 17%
Filesystem Metadata 1.44GB 0%
Inodes 542.8MB 0%
Snapshot Reserve 573.0GB 20%
Deduplication 4KB 0%
Snapshot Spill 818.4GB 29%
Quota Metadata 20KB 0%
Performance Metadata 2.27GB 0%
Total Used 1.83TB 65%
Total Physical Used 1.83TB 65%
::*> volume quota report -vserver svm02 -volume vol1
Vserver: svm02
----Disk---- ----Files----- Quota
Volume Tree Type ID Used Limit Used Limit Specifier
------- -------- ------ ------- ----- ----- ------ ------ ---------
vol1 xxxx tree 1 1.02TB 2.12TB 1385615 - xxxxx
Total snapshot utilisation is: 573GB + 818.4GB = 1.3TB
Total volume utilization = snapshot(1.3 TB) + qtree utilisation (1.02 TB from storage end) >>1.3 TB +1.02 TB = 2.32 TB
Total volume size available now to provision the quota is 2.80TB( total vol size) minus 2.32 TB(Current volume utilization on storage end)>>2.80TB -2.32TB = 0.48TB
Hence, at host end we see qtree size as 1.5 TB, volume space available + qtree utilization>> 0.48TB +1.02TB = 1.5 TB