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

VMware ESXi datastore free space not updating after volume size increase from the vCenter Server (52985)

Last Updated: 2/23/2024Categories: TroubleshootingTotal Views: 23923Language:
Chinese (Simplified)JapaneseEnglish

16 like this article

Subscribe to get an email
newsletter with new updates

16 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

After successfully increasing the volume size of a shared datastore from the vCenter Server 6.5.x and 6.7.x, you experience these symptoms:

Free space on the shared datastore fails to update on some of the ESXi hosts.

Shared datastore shows incorrect size on some of the ESXi hosts.

A storage vMotion to another destination datastore fails.

You see this error similar to:

Insufficient space on datastore

In the /var/log/vmkernel.log file of the ESXi host that reports the correct capacity of the shared datastore, you see entries similar to:

2017-11-02T19:38:04.126Z cpu12:77810 opID=9f937b12)World: 12230: VC opID IncreaseDatastoreWizard-apply-25137678-ngc:70327908-41-a9-eba3 maps to vmkernel opID 9f937b12
2017-11-02T19:38:04.126Z cpu12:77810 opID=9f937b12)LVM: 4014: [naa.xxxxxxxxxxxxxxxxxxxxx17:1] Device expanded (actual size 1572861919 blocks, stored size 1048573919 blocks)
2017-11-02T19:38:04.128Z cpu12:77810 opID=9f937b12)LVM: 4014: [naa.xxxxxxxxxxxxxxxxxxxxx:1] Device expanded (actual size 1572861919 blocks, stored size 1048573919 blocks)
2017-11-02T19:38:04.130Z cpu12:77810 opID=9f937b12)LVM: 14448: LVM device naa.xxxxxxxxxxxxxxxxxxxxx:1 successfully expanded (new size: 805305302528)
2017-11-02T19:38:04.142Z cpu12:77810 opID=9f937b12)Vol3: 1006: Unable to register file system Test for APD timeout notifications: Already exists
2017-11-02T19:38:04.144Z cpu12:77810 opID=9f937b12)LVM: 10661: Using all available space (268435456000).
2017-11-02T19:38:04.149Z cpu0:77810 opID=9f937b12)LVM: 10571: Successfully added space (0) on device naa.xxxxxxxxxxxxxxxxxxxxx :1 to volume 59fb71d0-f5ba54ed-79e7-f8bc12179f90

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

Purpose

This article provides information regarding issues where the ESXi fails to report the correct updated datastore capacity after a volume size increase in VMware vCenter Server 6.5.x and 6.7.x.

Cause

This issue occurs due a slow refresh call being made across all the ESXi hosts after an extend datastore operations from the vCenter Server successfully completes.

Resolution

This issue is resolved in:

VMware ESXi650-202007001 (Build 16576891), available at VMware Downloads.

VMware ESXi 6.7 Update 1, available at VMware Downloads.

Workaround

To work around this issue if you do not want to upgrade, VMware recommends to perform a cluster level rescan after expanding or increasing a datastore in the vCenter Server 6.5.x and 6.7.x. This forces the changes to all ESXi hosts that accesses the newly increased or expanded shared datastore.

Alternatively, run a Rescan Storage from the vSphere Client for each of the ESXi host not seeing the datastore size increase.

Log in as root on the ESXi host.

Check the datastore usage on the ESXi host by running this command:

df -h

Refresh the VMFS volume by running this command:

vmkfstools -v

Note: Perform this to all the ESXi host connected to the same shared datastore.

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)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant