Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vsanDatastore appears as 0 bytes in size following cluster membership changes (78062)

Last Updated: 6/8/2023Categories: TroubleshootingTotal Views: 13099Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

vSAN datastore appears as 0 B in size in the vSphere client but appears as normal size when checked from host Client or via SSH.

Purpose

This article details the cause and solution to one of the reasons a vSAN cluster's datastore may appear as 0 bytes, when checked via the vSphere client or CLI.

Cause

Hosts improperly added to or removed from a vSAN cluster can have vSAN enabled while they have no network access between all other hosts in the same cluster - from these hosts' perspective the vSAN datastore is 0B in size.

vSAN is a distributed storage system and each host connects with all other hosts to establish and build up the vSAN datastore. If one host is isolated from the rest of the cluster, it cannot bring the vSAN datastore on this specific host online and not contribute or consume any space.

vCenter uses random hosts to query datastores for its utilization, as vCenter does not have direct access to the underlying storage. Hence when vCenter chooses the isolated hosts, it will display the wrong size.

Impact / Risks

Provisioning of vSAN Objects (e.g. VMDK, snapshots, namespaces) may fail if the vSAN datastore appears as 0B in size.

Resolution

Identify any hosts that have been improperly added to or removed from the cluster that still have vSAN enabled but with no network connection to the other cluster members.

These can be identified via the vSphere client and validating that only the hosts that are part of the current vSAN cluster and have vSAN network configured appear here: Datastores > vsanDatastore > Hosts

If extraneous hosts that should not or do not have access to the datastore are listed then these still have vSAN enabled, this can be disabled via SSH to the host:
# esxcli vsan cluster leave

If you are unsure about making changes, please make changes during maintenance windows, if possible, or do consult VMware Support with the respective severity. Leaving hosts or changing the membership list can cause cluster partition and objects to go inaccessible.

Related Information

Note that there can be other causes of vsanDatastore appearing as 0 bytes, including cluster member(s) being network partitioned or the following issue:
vSAN cluster displays incorrect capacity information showing 0 Bytes used and 0 Bytes free

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 8.0.x

VMware vSAN 7.0.x

VMware vSAN 6.x

Take Our Survey

Support Assistant