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

ESXi 6.5 using VMFS-6 error: Insufficient disk space on datastore (51613)

Last Updated: 11/8/2023Categories: TroubleshootingTotal Views: 47974Language:
Chinese (Simplified)JapaneseEnglish

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Symptoms

This solution can also be used to address the problem before it starts complaining about space on the datastore. In this case, it would only have the symptom of not reclaiming the space on the array, and the following messages in vmkernel.log:

2017-10-05T01:56:38.713Z cpu3:66494)FSDisk: 300: Issue of delete blocks failed [sync:0] numDescs 1 Address is not aligned on required boundary 0x439540c9fb40

Creating or consolidating snapshots during Storage vMotion on ESXi 6.5 host using VMFS-6 fails with the error:

Insufficient disk space on datastore

The datastore has sufficient free space.

In the /var/log/vpxa.log file, you see entries similar to:

-->          message = "An error occurred while taking a snapshot: There is not enough space on the file system for the selected operation."
...
-->    msg = "Insufficient disk space on datastore ''."

In the /var/log/vmkernel.log file, you see entries similar to:

2017-10-05T01:56:38.713Z cpu3:66494)FSDisk: 300: Issue of delete blocks failed [sync:0] numDescs 1 Address is not aligned on required boundary 0x439540c9fb40
...
2017-10-05T02:10:04.623Z cpu6:2841554)Fil3: 8222: Max no space retries (10) exceeded for caller Fil3_FileIO (status 'No space left on device')

One or more datastore partitions have a Start Sector that is not aligned with a multiple of 1024.

For example:
# esxcli storage core device partition list
Device                                Partition  Start Sector  End Sector  Type  Size
-------------------------------------------------------------------------------------
naa.60030d90eb30aa06053e4105ddc052e0          1           128  4404019167    fb  2254857747968   MyBrokenDatastore
naa.60030d908cdc38043b69a7b3522416d9          1          2048  2726297567    fb  1395863305728   MyWorkingDatastore

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Resolution

This issue has been fixed in ESXi 6.5.0d, build-5310538, available at VMware Downloads. Upgrading to this version, or a newer version, will prevent new datastores from being created with the wrong start sector, but it will not fix existing datastores.

For long-term resolution, for those datastores that were already created with the wrong start sector (128), follow these steps:

Upgrade to ESXi 6.5.0d, build-5310538, or newer version of ESXi.

Create new datastores.

Migrate the VMs from the faulty datastores to the new datastores

Delete the faulty datastores.

After this is done, you should have no further troubles with automatic UNMAP, thus it will prevent the datastore disk space issue.

Workaround

To work around this issue:

From an ESXi host command line, you can fill the free space in the file system with zeros, using the esxcli storage vmfs unmap -u command:

For example: esxcli storage vmfs unmap -u 58e36bcd-396ca5a1-f37b-6c3be5b653b8

Note: Give the above task some time to complete, as the array will have some work to do, after the ESXi host command has completed the zero operation, and we cannot tell when the array gets done. Maybe wait until the next day. Then you can manually run the reclaim operation, mentioned in your storage array management software documentation, through the array management software.

Related Information

Thin Provisioning Block Space Reclamation (VAAI UNMAP) does not work

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
ESXi 6.0、6.5 で競合状態が発生し、仮想マシンまたは hostd 管理サービスが中断される (50372)

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

KB
•
Servicio de rendimiento: modo detallado en el servicio de estado de vSAN (51527)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant