Large ESA objects report as inaccessible with all components in an active state.

Products

• VMware vSAN

Issue/Introduction

Large ESA objects report as inaccessible with all components in an active state.

From vmkernel.log you see that zDOM is reporting no free segments and that there is no space left on device but the cluster has plenty of free space available. 

025-10-06T10:11:07.724Z In(182) vmkernel: cpu57:13505920)ZDOMObj_SegmentAllocWithRetry:1531: f2c1cd68-9876-97f7-9e11-###########: Wait for free segments. isBank=0
2025-10-06T10:11:07.724Z In(182) vmkernel: cpu57:13505920)ZDOMSegCache_GetOne:500: f2c1cd68-9876-97f7-9e11-###########: Failed to find a free segment leg=17723 (0 left)
2025-10-06T10:11:07.724Z In(182) vmkernel: cpu57:13505920)ZDOMObj_SegmentAllocWithRetry:1531: f2c1cd68-9876-97f7-9e11-###########: Wait for free segments. isBank=0
2025-10-06T10:11:07.724Z In(182) vmkernel: cpu57:13505920)ZDOMSegCache_GetOne:500: f2c1cd68-9876-97f7-9e11-###########: Failed to find a free segment leg=17723 (0 left)
2025-10-06T10:11:07.724Z In(182) vmkernel: cpu57:13505920)ZDOMObj_SegmentAllocWithRetry:1531: f2c1cd68-9876-97f7-9e11-###########: Wait for free segments. isBank=0
2025-10-06T10:11:07.724Z In(182) vmkernel: cpu57:13505920)ZDOMSegCache_GetOne:500: f2c1cd68-9876-97f7-9e11-###########: Failed to find a free segment leg=17723 (0 left)
2025-10-06T10:11:07.724Z In(182) vmkernel: cpu57:13505920)ZDOMObj_SegmentAllocWithRetry:1531: f2c1cd68-9876-97f7-9e11-###########: Wait for free segments. isBank=0
2025-10-06T10:11:07.724Z In(182) vmkernel: cpu57:13505920)ZDOMObj_SegmentAllocWithRetry:1553: f2c1cd68-9876-97f7-9e11-###########:dc6ac617: Reached max segment allocation retry limit
2025-10-06T10:11:07.724Z In(182) vmkernel: cpu57:13505920)ZDOMVatWriteBackSegment:2850: f2c1cd68-9876-97f7-9e11-###########: SetFailStop: No space left on device please check previous log for details
2025-10-06T10:11:07.724Z In(182) vmkernel: cpu57:13505920)ZDOMObjSetState:5602: f2c1cd68-9876-97f7-9e11-###########: zdom object set to fail-stop mode: No space left on device
2025-10-06T10:11:07.724Z In(182) vmkernel: cpu57:13505920)ZDOMObjHandleFSPUpdate:5407: f2c1cd68-9876-97f7-9e11-###########: reg-obj: update=0 useWorker=0 cleanupObj=1: No space left on device

The object that is reporting as inaccessible will also report as ZDOM_PAUSED

cmmds-tool find -f python -t ZDOM_PAUSED

[root@dfw-tx1-1da01-esxi-01:~] cmmds-tool find -t ZDOM_PAUSED

owner=00000000-0000-0000-0000-000000000000(Health: Unhealthy) uuid=f2c1cd68-9876-97f7-9e11-########### type=ZDOM_PAUSED rev=2 minHostVer=0 [content = (i1)], errorStr=(null)

Environment

VMware vSAN ESA ( Pre 8.0.3 P08 / 8.0U3i)

Cause

The object goes into an inaccessible state due to a miss-calculation of available space resources and this results in an out of space issue. 

Resolution

This issue has been been fixed in 8.0.3 P08 / 8.0U3i

If you run in to this issue please open a case with Broadcom Support for further investigation.