Skip to main content
NetApp Knowledge Base

How to check the tiered data size for FabricPool

Views:
1,634
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • FabricPool

Description

  • The USED size when running the command df 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.

  • 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]#

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.