Datastore Usage on Disk Alarm in vSphere: Resolving Capacity Issues

In this article, we will explore an issue where datastore capacity is incorrectly displayed in the vSphere web client and how it can be resolved.

Recently, I increased the capacity of one of my datastores from 1TB to 1.4TB, but the next day, the capacity reverted back to 1TB. This anomaly is not unique, as many administrators have encountered similar issues with incorrect datastore capacities in vSphere environments.

Another common problem related to VASA API version upgrades is that even after upgrading a registered VASA provider to support VASA API version 4.0, it still displays the previous version, such as 3.5. This issue can occur when upgrading a VMware vCenter system from a lower version, such as 7.x, to version 8.0.

To resolve these issues, administrators should navigate to the vSphere web client and select `vCenter Server > Configure > Storage Providers`. Then, expand the General tab of the registered VASA provider to check the current VASA API version. If it still displays an earlier version, such as 3.5, you may need to re-register the VASA provider or upgrade the vCenter system.

In some cases, a rare race condition can cause vCenter to report a failed update as successful, leading to errors in the software-packages.log files. These logs may contain error messages like 'No such file or directory: '/storage/core/software-update/install_operation''.

To resolve these issues, administrators should ensure that the VASA provider is properly registered and upgraded to support the latest VASA API version. Additionally, they should verify that the vCenter system is correctly configured and functioning as expected.

In conclusion, incorrect datastore capacity display and VASA API version upgrade issues are common problems in vSphere environments. By following these troubleshooting steps and best practices, administrators can resolve these issues and ensure the optimal performance of their VMware vSphere deployments.

Datastore usage on disk alarm in vsphere