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 disk at or above 99% utilization causes VM's to not be able to write to VMDK's. (77132)

Last Updated: 8/21/2023Categories: TroubleshootingTotal Views: 3580Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

A VM will crash when trying to write to a disk or fail to power on saying "no space left on device" when there is clearly still plenty of available space on the vSAN datastore. In the vmkernel log, you may see messages similar to the following.

2020-01-30T23:49:23.758Z cpu0:2097446)FS3DM: 2868: status No space left on device zeroing 1 extents (1048576 each)
2020-01-30T23:49:23.758Z cpu0:2097446)FS3J: 3104: Aborting txn (0x430dbf9c1e70) callerID: 0xc1d00006 due to failure pre-committing: No space left on device
2020-01-30T23:49:54.543Z cpu9:2097446)FS3DM: 2868: status No space left on device zeroing 1 extents (1048576 each)
2020-01-30T23:49:54.543Z cpu9:2097446)FS3J: 3104: Aborting txn (0x430dbf9c1e70) callerID: 0xc1d00006 due to failure pre-committing: No space left on device
2020-01-30T23:50:26.109Z cpu9:2097446)FS3DM: 2868: status No space left on device zeroing 1 extents (1048576 each)
2020-01-30T23:50:26.109Z cpu9:2097446)FS3J: 3104: Aborting txn (0x430dbf9c1e70) callerID: 0xc1d00006 due to failure pre-committing: No space left on device

Cause

This is caused if the vmdk resides on the disk that is at or above 99%. When there is a vSAN disk at or above 99% utilization, it can cause VM's to not be able to write to VMDK's even though there is still ample space available on the vSAN datastore.

Resolution

To work around this, identify the disk that is full using the following command in RVC.

vsan.disks_state .

Alternatively, from an ESXi host 6.5U1 or higher:

esxcli vsan debug disk overview

Once the disk above 99% has been identified,

Put the host into maintenance mode with Ensure Accessibility

Remove the disk from the Disk Group with No Action if Dedup is not enabled

After the disk has been removed, re-add the disk to the original Disk Group.

If Dedup is enabled, destroy and recreate the disk group.
Remove Disk Groups or Devices from vSAN
Recreate a Disk Group

This will force the objects to rebuild on other disks in the cluster. After this, the VM should be able to power on and write to the previously affected VMDK.

Related Information

How to manually remove and recreate a vSAN disk group using esxcli (2150567)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
「すべてのホストに Virtual SAN の vmknic が設定されています (All hosts have a Virtual SAN vmknic configured)」という誤った vSAN 健全性チェックのアラーム (67736)

KB
•
vSAN 延伸集群 - 共享见证集群数据主机数超出限制 (80774)

KB
•
vSAN Health Service - 物理磁盘运行状况 - 组件元数据运行状况 (2108912)

Results 1-4 of 4

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

Take Our Survey

Support Assistant