vVol reporting 0 size for capacity

Products

• VMware vCenter Server

Issue/Introduction

vVol datastore is showing as zero in capacity in vCenter.

Environment

VMware vCenter 7.0

VMware vCenter 8.0

Resolution

• SSH to the affected ESXi host and run the command esxcli storage core adapter list to see if the capability is reported as “Second Level Lun ID”. If these are not updated, ESXi will not be able to see sub-luns (vVols) in the SCSI path. Verify the HBA drivers are up to date on the ESXi hosts.
• The vVol daemon needs to be restarted in the ESXi host. You can do this by running the following in ESXi via SSH: /etc/init.d/vvold restart
• The ESXi host cannot talk to the VASA provider, use NC to make sure it can talk to it via port 8084 by running this command from SSH: nc -zv <vasa IP> 8084
• If an error similar to this appears: "nc: connect to x.x.x.x port 8084 (tcp) failed: Connection timed out" , check any external firewalls to ensure traffic can reach port 8084.

Also check the following:

VASA Provider Registration Problems
If the VASA provider isn't properly registered in vCenter, the vVol datastore may display incorrect capacity or even show zero available space.  Try to remove and re-add the VASA provider from the vCenter to see if that resolves the problem.

VASA Provider Connection Issues 
If the affected vCenter lost communication with the VASA provider, it could be failing to retrieve accurate statistics for the vVol datastore.

Metadata Sync Delays
Enhanced Linked Mode (ELM) relies on synchronization between vCenters. If there was a temporary sync issue, one vCenter may have had outdated metadata for the vVol datastore, causing it to report incorrect capacity.

Protocol Endpoint Recognition Issues
Some users have reported missing protocol endpoints (PEs), preventing vCenter from accurately detecting the vVol datastore.

NVMe/FC Configuration Mismatches
If the storage network is set up for NVMe/TCP while vCenter expects NVMe/FC, accessibility issues can arise.

If using PURE storage:

Differences in Storage Reporting
Pure Storage uses compression and deduplication, which can sometimes result in discrepancies between the capacity reported by vCenter and the actual available storage on the array.

Temporary Storage Container Context Failures
Some logs indicate errors related to the storage container context settings, which may explain the fluctuating capacity observed during the specified timeframe.

It may be helpful to verify the following:

• Ensure the VASA provider is correctly registered.
• Check for inconsistencies in protocol configurations.
• Review logs for any transient failures related to the storage container context.
• Upload a copy of the vm-support logs from one of the hosts so transient storage errors at the host level can be reviewed.