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

vSAN Health Service - Capacity utilization - Disk space (71003)

Last Updated: 5/19/2023Categories: InformationalTotal Views: 42723Language:
Chinese (Simplified)JapaneseEnglish

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Details

This article explains the Capacity Utilization Health – Disk Space check in the vSAN Health Service and provides details on why it might report an error.

Solution

Q: What does the Capacity utilization health – disk space check do?

This particular health check looks at cluster level disk usage and ensures it doesn't exceed the threshold.

Q: What does it mean when it is in an error state?

For vSAN, If this check has a warning or error, it may means there is no enough free storage capacity and the deployment of new virtual machines may fail, or any component rebuild operations may not be allowed. If the cluster is running out of space, like exceeding 99% full, the running virtual machines may crash with pending question and any R/W IO may fail.

For vSAN Direct, if this check has a warning or error, it may mean there is no enough free storage capacity, and the creation of CNS volumes may fail.

Thresholds definition

On this page, vSAN ops threshold and host rebuild threshold are defined as below:

vSAN ops threshold = Total space - Operations reserve

Host rebuild threshold = Total space - Operations reserve - Host rebuild reserve

* Note that in some cases the Host rebuild threshold can be equal to the vSAN ops threshold, such as in VMC deployments, because the feature of host rebuild reserve is not needed for VMC deployments.

The thresholds definition is:

When host rebuild reserve is disabled:

Red: MIN(90% of total capacity, vSAN ops threshold)

Yellow: = MIN(70% of total capacity,  Host rebuild threshold)

When host rebuild reserve is enabled:

Red: MIN(90% of total capacity, Host rebuild threshold)

Yellow: = MIN(70% of total capacity,  80% of Host rebuild threshold)

Q: How does one troubleshoot and fix the error state?

The first step is to ensure that all the storage is valid, that there are no missing capacity devices, and ensure that the vSAN datastore capacity is what you expect it to be. There a 3 options to recover a full vSAN datastore situation as detailed below:

Download VM(s) to local workstation to free up space on vSAN datastore:

Identify the full disk/diskgroup.

Identify VM(s) residing on the full diskgroup.

VM must be healthy. If they are orphaned or inaccessible, then select a different VM to free up space.

VM must have namespace reservation usage of less than 10MB.

Power off [for VMs with a pending question, answer 'cancel'].

There may be multiple questions - all must be answered.

If hostd is non-responsive/hung, this method may not work.

Download the VM to your local workstation.

verify download is complete and contains all VM data.

Delete the VM on vSAN.

Power-off VMs to free up resources on vSAN:

Gracefully power off VM(s). This will delete the swap files associated with those guests and free up some space.

Once enough VMs have been powered off, svMotion VMs to alternate storage.

If alternate storage is not available, delete unnecessary guests to free up additional space.

Expand vSAN Direct datastore capacity.
If vSAN servers have available slots for additional drives and disks are available, add disks to the vSAN Direct storage to expand capacity. This is typically the easiest option if the appropriate resources are available.

Caveats

vSAN has limited functionality when full.

When diskgroups in the cluster are full, VMs that reside on those diskgroups will experience failures for any operations that require space, such as storage vMotion. Other operations may take significantly more time to complete than they would in a healthy cluster.

Recovered space may not be reflected in the UI.

When pursuing methods of recovery that delete swap files above, manually confirm via CLI.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

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.7.x

Take Our Survey

Support Assistant