BugZero | VMware vCenter BugID b4b3287def2b - After recovering from APD or PDL conditions, VMFS ...

VMware vCenter - Defect ID: b4b3287def2b

After recovering from APD or PDL conditions, VMFS datastore with enabled support for clustered virtual disks might remain inaccessible

VMware vCenter - Defect ID: b4b3287def2b

After recovering from APD or PDL conditions, VMFS datastore with enabled support for clustered virtual disks might remain inaccessible

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: b4b3287def2b

Overview

You can encounter this problem only on datastores where the clustered virtual disk support is enabled. When the datastore recovers from an All Paths Down (APD) or Permanent Device Loss (PDL) condition, it remains inaccessible. The VMkernel log might show multiple SCSI3 reservation conflict messages similar to the following: 2020-02-18T07:41:10.273Z cpu22:1001391219)ScsiDeviceIO: vm 1001391219: SCSIDeviceCmdCompleteCB:2972: Reservation conflict retries 544 for command 0x45ba814b8340 (op: 0x89) to device "naa.624a9370b97601e346f64ba900024d53" The problem can occur because the ESXi host participating in the cluster loses SCSI reservations for the datastore and cannot always reacquire them automatically after the datastore recovers.

Workaround

Manually register the reservation using the following command: vmkfstools -L registerkey /vmfs/devices/disks/<device name> where the <device name> is the name of the device on which the datastore is created.

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: 3080596
During the generation of a new image recommendation by the vSphere Lifecycle Manager, the vpxd service fails due to memory exhaustion
Defect ID: 3020259
You cannot remove a PCI passthrough device assigned to a virtual Non-Uniform Memory Access (NUMA) node from a virtual machine with CPU Hot Add enabled
Defect ID: 3280955
You see incorrect Maximum Size value for thin-provisioned virtual disks
Defect ID: 2ca773f4bc25
The PCI slot of a virtual device might change after upgrade from hardware version 19
Defect ID: 3308624
ESXi hosts fail to boot with an error such as Could not boot image: Invalid argument (http://ipxe.org/err/1c0de8)

Ready to prevent the next vendor outage?

Get a demo

VMware vCenter - Defect ID: b4b3287def2b

After recovering from APD or PDL conditions, VMFS datastore with enabled support for clustered virtual disks might remain inaccessible

VMware vCenter - Defect ID: b4b3287def2b

After recovering from APD or PDL conditions, VMFS datastore with enabled support for clustered virtual disks might remain inaccessible

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