ONTAP Discussions

Discrepancies with the DF & DF -A Output

armandol
2,397 Views

I am trying to determine why the total "consumed" volume space shown in the df command does not add up to the used space show in the df -A command. I have two volumes in

an aggregate one has the space guarantee set to volume and the other has the space guarantee set to none.

I have added up the "used" column for the volme with space guarantee set to none and the "kbytes: column for the volume that has the space guarantee set to volume and the numbers do not add up to the used aggregate space in the df -A command.

Can some please explain to me what I am doing wrong.

All help is greatly apprecaited

Aggregate Used Space = 1.02TB

Volume vditemplate01 space (guarantee=volume) = 200GB

Volume vdids3PCC1 space (guarantee=none) = 773GB

Total = 973

===== DF-A =====
Aggregate               kbytes       used      avail capacity 
aggr1               5238716824 1095885552 4142831272      21% 
aggr1/.snapshot      275721936  118478352  157243584      43%

===== DF =====
Filesystem              kbytes       used      avail capacity  Mounted on
/vol/vditemplate01/  209715200   28196880  181518320      13%  /vol/vditemplate01/
/vol/vditemplate01/.snapshot          0          0          0     ---%  /vol/vditemplate01/.snapshot
/vol/vdids3PCC/     1610612736  810128928  800483808      50%  /vol/vdids3PCC/
/vol/vdids3PCC/.snapshot          0          0          0     ---%  /vol/vdids3PCC/.snapshot

Aggr1 Volumes
=============
Volumes: vditemplate01, vdids3PCC

Space Guarantee
===============
Volume State           Status            Options          
      vdids3PCC online          raid_dp, flex     nosnap=on, no_atime_update=on,
                                sis               create_ucode=on, guarantee=none

  vditemplate01 online          raid_dp, flex     nosnap=on, no_atime_update=on,
                                sis               create_ucode=on

1 REPLY 1

djaquays0
2,398 Views

There's a similar discrepency on our filers as well.  I would assume it's related to deduplication metadata, as that's stored outside of the volume, and whatever other data NetApp stores outside of the volume.

Public