From my experience, the netapp cli command "vol size" returns size in the units in which size was set. In other words, if I enter "vol size vol1 1200g" and then enter the command "vol size vol1," I will expect a result of "1200g".
The command "df vol1" would return size in kibibytes (KiB) or 1024 bytes. The commandled "Get-NaVolSize vol1" command returns the size in bytes.
For example, here are the outputs for various commands in my environment for a volume named "vol1" (the volume name and NetApp names have been changed). The volume size was set previously to 200g by using the command "vol size vol1 200g"
Adai, the design point for the PowerShell Toolkit is to report all sizes, rates, etc. in bytes unless specifically stated otherwise. The data formatters do reduce those to human-readable values with units, and the setter cmdlets accept both byte values as well as values with units. The Toolkit invokes Data ONTAP APIs in most cases, rather than calling the CLI, but the Toolkit and CLI should obviously return the same results.
Say i create a volume snapmirror between two filers f1 and f2.In order to make sure that the VSM update always succed and to avoid constant resizing of the vsm destination volume I create the volume to the size of the aggr.
So if i have a source volume f1:v1 of 10g and aggr on filer f2: of size 100G. now in order to create a VSM destination volume on filer f2 i create a volume v2 of size 100G with guarntee set to none.
Now, once the VSM baseline is completed. On the destination filer f2.
df -h will give the size of f2:v2 as 10G( same as source)
vol size v2 will give the size as 100G( the size to which it was created)
so my question now is does running Get-NaVolSize will it reutrn 10g or 100G ?
I am looking for the command that will list 100G and not 10G.