How to check the tiered data size for FabricPool
Applies to
- ONTAP 9
- FabricPool
Description
- The
USED
size when running the commanddf
on a FabricPool volume is different than the parent FabricPool aggregate.- For example, in the below output the aggregate used space is 0GB:
cluster01::> df -A -g aggr2
Aggregate total used avail capacity
aggr2 2413GB 0GB 2413GB 0%
aggr2/.snapshot 0GB 0GB 0GB 0%
2 entries were displayed.
However, the volume reports the used space as 9GB:
cluster01::> df -g siva
Filesystem total used avail capacity Mounted on Vserver
/vol/siva/ 9GB 9GB 0GB 99% /siva svm1
/vol/siva/.snapshot 0GB 0GB 0GB 0% /siva/.snapshot svm1
2 entries were displayed.
- The
df
command at the volume level includes the tiered data for the used space and no data can be added beyond the actual volume size. Volume can be over-subscribed to account for the tiered data. - This causes the client to report no space left on the device, even though all the 9GB is tiered out:
[nfs_client]# df -h /mydata
Filesystem Size Used Avail Use% Mounted on
svm1:/siva 9.5G 9.5G 12M 100% /mydata
[nfs_client]#
[nfs_client]# cp mydatafile.log /mydata
cp: error writing /mydata/mydatafile.log: No space left on device
cp: failed to extend /mydata/mydatafile.log: No space left on device
[nfs_client]#