Loading

×Sorry to interrupt
CSS Error

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

Cluster wide storage rescan from vCenter Server causes ESXi/ESX hosts and virtual machines to become unresponsive (1039088)

Last Updated: 2/23/2024Categories: TroubleshootingTotal Views: 25530Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

During a VMFS refresh you experience these symptoms:

Virtual machines become unresponsive to ping requests for a prolonged period of time.

Virtual machines are inaccessible for a prolonged period of time.

You are unable to access virtual machines.

A large number of volumes (more than 50) are presented to more than 10 hosts in the cluster at the same time.

A cluster wide storage rescan from vCenter Server causes the ESXi/ESX hosts to go into a "not responding" state for approximately 5 to 10 minutes.

Direct connection to a host using the vSphere Client fails.

A datastore rename task or adding a new datastore can trigger a cluster wide rescan which causes hosts to become unresponsive.

Virtual machines in vCenter Server become orphaned.

After 5 to 10 minutes, the hosts automatically start responding again without any user intervention.

In the vmkernel.log file or the messages file (located at /var/log/), these events appear during the rescan:

cpu5:4181)FS3: 3002: [Req mode: 1] Checking liveness of [type 10c00002 offset 12750848 v 18438, hb offset 3743744
gen 39693, mode 1, owner 50126535-b61b9026-xxxx-5ef3fc226207 mtime 6672253] on vol 'datastore'
cpu5:4181)FS3: 3100: [Req mode: 1] Lock [type 10c00002 offset 12750848 v 18438, hb offset 3743744
gen 39693, mode 1, owner 50126535-b61b9026-xxxx-5ef3fc226207 mtime 6672253] is not free on vol 'datastore'
cpu5:4181)FS3: 3002: [Req mode: 1] Checking liveness of [type 10c00002 offset 12750848 v 18438, hb offset 3743744
gen 39693, mode 1, owner 50126535-b61b9026-xxxx-5ef3fc226207 mtime 6672253] on vol 'datastore'
cpu0:4181)FS3: 3100: [Req mode: 1] Lock [type 10c00002 offset 12750848 v 18438, hb offset 3743744

Cause

This issue occurs when multiple hosts try to allocate or deallocate an object or a series of objects in a VMFS filesystem. This causes resource contention for hostd and virtual machine userworlds.

These actions can trigger this issue:

Adding a new VMFS datastore from vCenter Server

Removing an existing VMFS datastore from vCenter Server

Performing a cluster wide rescan for new storage devices and/or VMFS datastores

Note: This issue can also affect dependent products, such as Site Recovery Manager and vSphere Replication.

Resolution

This issue is resolved in:

VMware ESXi 5.5, Patch Release ESXi550-201312001 (2063795)

VMware ESXi 5.1, Patch ESXi510-Update02: ESXi 5.1 Complete Update 2 (2062314)

VMware ESXi 5.0, Patch ESXi500-201308401-BG: Updates esx-base (2053133)

VMware ESXi 4.1, Patch Release ESXi410-201312401-SG: Updates Firmware (2061205)

VMware ESX 4.1, Patch Release ESX410-201312401-SG: Updates VMkernel, CIM, Tools, and others (2061196)

You can download the latest releases from the VMware download site.

To work around this issue when you are unable to apply a patch:

Run rescans from individual hosts one at a time using the vSphere Client or console. For more information, see Performing a rescan of the storage on an ESXi/ESX host (1003988).

Disable automatic rescan from vCenter Server. For more information, see How to disable automatic rescan of HBAs initiated by vCenter (1016873).

Reduce the number of LUNs/datastores that every host is seeing. For each host, only present the LUNs that the cluster hosts have virtual machines or RDMs on. Unpresent all the unused LUNs from the cluster.

Related Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box
Performing a rescan of the storage on an ESX/ESXi host
How to disable automatic rescan of HBAs initiated by vCenter Server
VMware ESXi 5.1, Patch ESXi510-201307401-BG: Updates esx-base and misc-drivers
VMware ESXi 5.0, Patch ESXi500-201308401-BG: Updates esx-base
VMware ESX 4.1, Patch Release ESX410-201312401-SG: Updates VMkernel, CIM, Tools, and others
VMware ESXi 4.1, Patch Release ESXi410-201312401-SG: Updates Firmware
VMware ESXi 5.1, Patch ESXi510-Update02: ESXi 5.1 Complete Update 2
VMware ESXi 5.5, Patch Release ESXi550-201312001

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
•
"Failed to execute operation: Unit file is masked」または「ErrCode: 111」エラーが、VCSA 6.X でのサービス開始時に発生する (52945)

KB
•
尝试从“vRA 基础架构”选项卡导出受管计算机列表时出现 “HTTP 状态 502 (HTTP Status 502)”错误 (52881)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware ESXi

Related Versions:

Take Our Survey

Support Assistant