BugZero | VMware vCenter BugID b3c90afb17d6 - ESXi host might get in non responding state if a n...

VMware vCenter - Defect ID: b3c90afb17d6

ESXi host might get in non responding state if a non-head extent of its spanned VMFS datastore enters the Permanent Device Loss (PDL) state

VMware vCenter - Defect ID: b3c90afb17d6

ESXi host might get in non responding state if a non-head extent of its spanned VMFS datastore enters the Permanent Device Loss (PDL) state

Last updated on January 19th, 2026

BugZero Risk Score
0.0 Coming soon

Overall: N/A

Severity: N/A

Community: N/A

Lifecycle: N/A

What is the BugZero Risk Score?

VMware vCenter Integration

Learn more about where this data comes from

VMware vCenter Integration

Learn more

Bug Scrub Advisor

Streamline upgrades with automated vendor bug scrubs

Bug Scrub Advisor

Learn more

BugZero Enterprise

Wish you caught this bug sooner? Get proactive today.

BugZero Enterprise

Learn more

Bug Details

Status: Known
Impact Category: Storage Issues
Workaround Available:

Description

Disclaimer

A custom bug ID has been generated as the vendor did not provide one: b3c90afb17d6

Overview

This problem does not occur when a non-head extent of the spanned VMFS datastore fails along with the head extent. In this case, the entire datastore becomes inaccessible and no longer allows I/Os. In contrast, when only a non-head extent fails, but the head extent remains accessible, the datastore heartbeat appears to be normal. And the I/Os between the host and the datastore continue. However, any I/Os that depend on the failed non-head extent start failing as well. Other I/O transactions might accumulate while waiting for the failing I/Os to resolve, and cause the host to enter the non responding state.

Workaround

Fix the PDL condition of the non-head extent to resolve this issue.

Bug URLs

https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-70u3v-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3l-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3m-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3n-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3o-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3p-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3q-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3r-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3s-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3u-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3w-release-notes.html

Relevant Products

Click on a version to see all relevant bugs

Affected versions:7.0.3.01400, 7.0.3.01500, 7.0.3.01600, 7.0.3.01700, 7.0.3.01800, 7.0.3.01900, 7.0.3.02000, 7.0.3.02100, 7.0.3.02300, 7.0.3.02400, 7.0.3.02500

Fixed versions: No known fixed versions

Relevant Products

Click on a version to see all relevant bugs

Affected versions:7.0.3.01400, 7.0.3.01500, 7.0.3.01600, 7.0.3.01700, 7.0.3.01800, 7.0.3.01900, 7.0.3.02000, 7.0.3.02100, 7.0.3.02300, 7.0.3.02400, 7.0.3.02500

Fixed versions: No known fixed versions

Top VMware vCenter Defects

Defect ID: 3557847
Missing logs in the vCenter log file for vSAN health
Defect ID: 3488172
Login instructions for RSA SecurID Authentication in the vSphere Client might display HTML tags as plain text
Defect ID: 3484244
A rare race condition might cause repeating failovers due to a failure of the vCenter vpxd service or vSphere Client becoming unresponsive
Defect ID: 68adfd8f5272
vSphere Storage vMotion operations might fail in a vSAN environment due to an unauthenticated session of the Network File Copy (NFC) manager
Defect ID: 524f315fc61b
You see large threadmonitor<num>.log files in the vsphere-ui logs directory

Ready to prevent the next vendor outage?

Get a demo

VMware vCenter - Defect ID: b3c90afb17d6

ESXi host might get in non responding state if a non-head extent of its spanned VMFS datastore enters the Permanent Device Loss (PDL) state

VMware vCenter - Defect ID: b3c90afb17d6

ESXi host might get in non responding state if a non-head extent of its spanned VMFS datastore enters the Permanent Device Loss (PDL) state

Last updated on January 19th, 2026

BugZero Risk Score0.0 Coming soon

Bug Details

Disclaimer

Overview

Workaround

Bug URLs

Top VMware vCenter Defects

Ready to prevent the next vendor outage?

Links

BugZero Risk Score
0.0 Coming soon