This is expected behaviour.
You will note that there are no -flat.vmdk files there which is what you are probably thinking of showing as of size - vSAN doesn't use -flat.vmdk, vmdks are stored as Objects and the .vmdk is just a text file describing the attributes of the vmdk Object.
Thanks Bob, I noticed that and suspected the same.
Is there an interface to see how big VMDKs are getting? Or is it just a case of looking at the VM summary etc. and seeing how much space a particular VM is consuming?
"Is there an interface to see how big VMDKs are getting? Or is it just a case of looking at the VM summary etc. and seeing how much space a particular VM is consuming?"
There are numerous ways of getting the used size of VMs/vmdks:
- vSphere Client(s) summary of VM usage - this includes space used by all disks/snapshots/vswp/vmem and also the replica method overhead for each(e.g. 2x for RAID1).
- FLEX Client (maybe HTML5 also in later versions) Right-click VM > Edit Settings > Hard disk X > 'vSAN storage consumption' shows good break-down per disk.
- vSphere Client(s) Cluster/Host > VMs > Virtual Machines > 'Used Space' tab
- vSphere Client(s) Home > Policies and Profiles > Storage Policy X > VMs > Virtual Machines > 'Used Space' tab
- Via RVC > vsan.vm_object_info <pathToVM>:
- Via CLI using output from #esxcli vsan debug object list - this can be handy if you are somewhat proficient at basic scripting to generate periodic reports.
- PowerCLI - I am positive there numerous ways to approach this, have a look on that sub-community for some ideas/examples.