Skip to main content
NetApp Knowledge Base

VASA Provider: vCenter not accurately reporting VMs' used space compared to the backing vVol's available space

  1. Last updated
  2. Save as PDF
Views:
21
Visibility:
Public
Votes:
0
Category:
netapp-vasa-provider
Specialty:
virt
Last Updated:

Applies to

  • NetApp VASA Provider 
  • VMware ESXi 8.0u1 and later

Issue

  • Users report discrepancies between what their vVol datastores show for the available space compared to the consumed space their VMs show in vCenter.
  • This is due to the config-vvol objects that are created on the backed storage array when VMs are placed onto the vVol datastore.
  • Config-vvvols store the essential metadata and configuration files for a VM, such as .vmx, nvram, and log files.
  • In ESXi 8.0.U1, the new config vVol objects by default are created as 255 GB thin provisioned vVols instead of 4GB thin provisioned vVols in earlier versions of ESXi.
  • Config-vvol objects can add up the more VMs that are placed onto a vVol datastore which in turn can consume more space than what is reported in vCenter.

 

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.