Why is volume total space larger than aggregate allocated space?
Applies to
- ONTAP 9
- Data ONTAP 8 7-Mode
Answer
- Before calculating the volume space consumed in the aggregate, check the volume option as below:
fs_size_fixedNodeName> vol status -v voldp
Volume State Status Options
voldp online raid_dp, flex nosnap=off, nosnapdir=off, minra=off,
snapmirrored no_atime_update=off, nvfail=off,
read-only ignore_inconsistent=off, snapmirrored=on,
64-bit create_ucode=off, convert_ucode=off,
maxdirsize=73400, schedsnapname=ordinal,
fs_size_fixed=on, guarantee=volume,filesys-size-fixedClusterName::> volume show -volume voldp -fields filesys-size-fixed
vserver volume filesys-size-fixed
------- ------- ------------------
svm1 voldp True- If the status is 'On/True,' the volume file system is fixed. It does not reflect the real size occupied by the aggregate.
- If the volume is read/write, turn it to 'Off/False' to check the volume space consumption by the aggregate.
Additional Information
volume modify
[-filesys-size-fixed {true|false}] - Is File System Size Fixed
This parameter is only applicable for a DP relationship.
This option causes the file system to remain the same size and not grow or shrink when a SnapMirrored volume relationship is broken, or when a volume add is performed on it.
It is automatically set to true when a volume becomes a SnapMirrored volume.
It stays set to true after the snapmirror break command is issued for the volume.
This allows a volume to be SnapMirrored back to the source without needing to add disks to the source volume.
If the volume is a flexible volume and the volume size is larger than the file system size, setting this option to false forces the volume size to equal the file system size.
The default setting is false