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

Skip to main content

My Subscriptions

Loading

Knowledge Base

Extending or increasing a datastore through vCenter Server fails (1011754)

Last Updated: 6/3/2022Categories: TroubleshootingTotal Views: 278171Language:
Chinese (Simplified)JapaneseSpanishEnglish

64 like this article

Subscribe to get an email
newsletter with new updates

64 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 extending or increasing a datastore from the VMware vCenter Server using the vSphere Client, you experience these symptoms:

The extend or increase datastore task fails.

The vCenter Server fails to display the available unused disk space capacity.

After extending the LUN from the SAN, the new storage appears under Storage Adapters when viewed from the vCenter Server. However, the increased disk space is not showing or not available through the datastore properties.

The expanded or increased datastore capacity is empty.

Purpose

This article provides steps to resolve an issue where the added disk space is not visible, or the datastore capacity is empty after extending or expanding a datastore through the vCenter Server using the vSphere Client.

Cause

The VMware vCenter Server calls a specific function to get all the available extents for that datastore. After getting these extents, the vCenter Server displays these extents as available after meeting these following criteria filters:

LUNS are used as datastores on that ESXI host or on any other ESXi host (with exceptions to force mounted volumes).

LUNS are not used as Raw Device Mapping (RDMs) on that ESXi host or any other ESXi host.

LUNs are seen the same by all hosts.

Notes:

The vCenter Server applies these filters to stop any possible data corruption on already used LUNs by other host.

You can validate these from the vpxd logs with these steps:

Review LUN IDs for the LUNs in question on all hosts to make sure they are consistent.

Enable verbose logging for the vpxd logs and attempt to expand/increase the datastore. For more information, see the Set Verbose Logging section of the vSphere Monitoring and Performance Guide.

In the vpxd.log file, you see entries similar to:

[QueryAvailableDisksForVmfs] Removed all candidates because all LUNs in the datastore are not visible by the same hosts or have the same transport types

Important: VMware recommends not to turn off the filters. Disabling these filters may result in storage device corruption or performance degradation. For more information, see the Storage Filtering section of the vSphere Storage Guide.

Resolution

NOTE: Before starting, verify LUN presentation is the same on all hosts as this is a common, legitimate cause and should not be worked around.

To resolve this issue, follow either one of the two options:

Increase or expand the datastore directly from the ESXi host

From the Web Client, right click the ESXi host and select Storage > Rescan Storage. This forces the ESXi host to sync with the changes on the underlying expanded devices.

Once the rescan storage completes, navigate to the Datastore View and select the increased or expanded datastore.

Navigate to Configure > Device Backing and select Extent Name. You should see the Device Details reflecting the updated capacity from the expansion that was done from the SAN.

Note: In this example, the datastore iscsi1 was configured for 25GB and the underlying device was expanded to 400GB.

If the underlying device does not reflect the underlying information, attempt another host level rescan so that the fields highlighted in the image above indicate the desired change. Only follow these steps if the increase in the capacity of the underlying device is detected:

Log in directly to one of the ESXi host that has access to the datastore through the GUI (Host Client) using root credentials.

Navigate to Storage > Datastores and select the datastore you are trying to expand or increase.

Right-click on the datastore and select Increase Capacity. Alternatively, select the Increase capacity button.

You should be prompted to select one of two options:

Add an extent to existing VMFS datastore
Expand an existing VMFS datastore extent

Note: The first option is to create a multi-extent datastores by spanning (adding) a new volume to the existing datastore. The second option is to increase the capacity for the existing device itself. In this example, the second option is used:

Select the VMFS partition as highlighted in the image and use the side-scroller to indicate the range of the expansion that would need to be done and click Next.

Click Finish. You should now be able to view the datastore expansion as completed.

Immediately rescan all hosts by “rescan adapter” and “rescan vmfs” from vCenter.
Or by commands on all hosts:
$ esxcli storage core adapter rescan --all
$ vmkfstools -V

Important:
As this was done directly on the ESXi host, VMware recommends to do a cluster level storage rescan so that all of the ESXi host accessing the same datastore are sync with the expansion that was recently completed. If a cluster level rescan is not done from the vCenter Server, there is a good chance that the vCenter Server might not readily detect the changes which may lead to disparity in the current space/usage of the datastore. VMware recommends to always do a cluster level rescan on the vCenter Server level when the datastore is increased or expanded directly from the ESXi host.

Temporarily disable the Same Host and Transport Filter

Important: VMware does not recommend to turn off or disable this filter. After temporarily turning off or disabling this filter, increase or expand the datastore. Once this is completed, ensure this filter is turned back on or re-enabled. Disabling these filters may result in storage device corruption or performance degradation that might be caused by an unsupported use of storage devices. For more information, see or more information, see the Storage Filtering section in the vSphere Storage Guide.

Look for parameter config.vpxd.filter.sameHostsAndTransportsFilter under Advanced vCenter Server Settings and set it to false.

Do not add the parameter if it already exists, as adding a duplicate parameter can cause vCenter instability. Instead, edit the existing parameter.

Note: No reboot is required for changes to take into effect. Logging out and logging back in to the vCenter Server should be enough for changes to take into effect.

Once completed, change config.vpxd.filter.sameHostsAndTransportsFilter under Advanced vCenter Server Settings and set it to true. For more information, see the Storage Filtering section of the vSphere Storage Guide.

Related Information

VMware Skyline Health Diagnostics for vSphere - FAQ

LUN filtering mechanism during RDM creation

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseSpanishEnglish

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

VMware vSphere ESXi

VMware vCenter Server

VMware ESXi

Related Versions:

VMware vSphere ESXi 7.0.x

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

VMware vCenter Server 7.0.x

VMware vCenter Server 6.7.x

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant