Unable to place ESXI host in maintenance mode due ObjectCheckConfigLimitCB: Object ################ has exceeded maximum number of components per object (2040)
search cancel

Unable to place ESXI host in maintenance mode due ObjectCheckConfigLimitCB: Object ################ has exceeded maximum number of components per object (2040)

book

Article ID: 440928

calendar_today

Updated On:

Products

VMware vSAN 8.x

Issue/Introduction

  • ESXI host unable to enter to maintenance mode with ensure accessibility 
  • Object reaching component limit due storage policy in use and virtual machine disk size 
  • Resync stuck unable to clean up transient components 

Environment

VMware vSAN 8.x

 

Cause

  • Transient Components: Running esxcli vsan debug object list -u ####-####-####-####-#### reveals objects with transient components.

               RAID_1
                  Component:  #####-###-####-####-#####
                    Component State: ACTIVE, Address Space(B): 205353123840 (191.25GB), Disk UUID:  #####-###-####-####-#####, Disk Name: naa.##################, Transient: 1
                    Votes: 1, Capacity Used(B): 53372404608 (49.71GB), Physical Capacity Used(B): 66938339328 (62.34GB), Total 4K

  • Component Limits: The /var/run/log/clomd.log file shows the object exceeding the maximum threshold:

2026-04-22T13:33:33.557+0100 Cr(26) clomd[2100901]: [Originator@6876 opID=########] ObjectCheckConfigLimitCB: Object  #####-###-####-####-##### has exceeded maximum number of components per object (2040).
2026-04-22T13:33:33.589+0100 Cr(26) clomd[2100901]: [Originator@6876 opID=########] ObjectCheckConfigLimitCB: Object  #####-###-####-####-##### has exceeded maximum number of components per object (2040).
2026-04-22T13:33:33.589+0100 Cr(26) clomd[2100901]: [Originator@6876 opID=########] CLOM_FixObjectWrapper: StepFix failed for object #####-###-####-####-##### Too many elements for list

 

  • Resync Failures: The /var/run/log/clomd.log confirms a DECOM_STATE_FAILED status because the cleanup process cannot proceed due to component limits.

2026-04-21T08:51:09.705Z No(29) clomd[2100902]: [Originator@########] CLOMDecomCMMDSResponseCb: Node  #####-###-####-####-#####: CMMDS published decom state DECOM_STATE_CLEANUP Pending decom state DECOM_STATE_INVALID
2026-04-21T08:51:09.705Z No(29) clomd[2100902]: [Originator@########] CLOMDecomPublishDecomStateEntryInt: Node #####-###-####-####-#####: Publishing state DECOM_STATE_FAILED
2026-04-21T08:51:09.705Z No(29) clomd[2100902]: [Originator@########] CLOMDecomPublishDecomStateEntryInt: Node #####-###-####-####-#####: Published state DECOM_STATE_FAILED. Affected objects: 0, Progress: 10, Update: 1, numObjectsEvacuated 350, totalObjectstoEvacuate 350, bytesToSyncRemaining 0, totalBytesToSync 0
2026-04-21T08:51:09.713Z No(29) clomd[2100902]: [Originator@########] CLOM_ProcessDecomUpdate: Node #####-###-####-####-##### state change. Old:DECOM_STATE_CLEANUP New:DECOM_STATE_FAILED Mode:1 evacReason:0 JobUuid #####-###-####-####-#####

2026-04-21T08:58:58.579Z No(29) clomd[2100902]: [Originator@########] CLOM_PostWorkItem: Posted a work item opID: #####-###-####-####-##### group: 00000000-0000-0000-0000-000000000000 Type: CLEANUP delay 0 (Success)
2026-04-21T08:58:58.591Z No(29) clomd[2100902]: [Originator@########opID=########] CLOMProcessWorkItem: Op CLEANUP starts:1804289448
2026-04-21T08:58:58.598Z No(29) clomd[2100902]: [Originator@########opID=########] CLOMReconfigure: Reconfiguring #####-###-####-####-##### workItem type CLEANUP
2026-04-21T08:58:58.619Z Cr(26) clomd[2100902]: [Originator@########opID=########] ObjectCheckConfigLimitCB: Object  #####-###-####-####-##### has exceeded maximum number of components per object (2040).
2026-04-21T08:58:58.626Z No(29) clomd[2100902]: [Originator@########opID=########] CLOMSetQuorumVotes: Counted votes good:6, absent:0, bad:0; upperFDs:2, minLowerFDs:3, nTotalReplicas:6, nUpperReplicas:2, nLowerReplicas:3
2026-04-21T08:58:58.626Z No(29) clomd[2100902]: [Originator@########opID=########] CLOMSetQuorumVotes: 1 upper primary witnesses are required
2026-04-21T08:58:58.626Z No(29) clomd[2100902]: [Originator@########opID=########] CLOMSetQuorumVotes: Need at least 5 Lower FDs Per Upper, current: 3
2026-04-21T08:58:58.626Z No(29) clomd[2100902]: [Originator@########opID=########] SetVotes: Balance votes - twoLevelVoteAssignment:TRUE minimalVotesPerUpper:5 targetVotesPerUpperFD:5 numUpperFDs:3
2026-04-21T08:58:58.626Z No(29) clomd[2100902]: [Originator@########opID=########] CLOMStepFixObject: Fixing Concat leg : 0
2026-04-21T08:58:58.649Z Cr(26) clomd[2100902]: [Originator@########opID=########] ObjectCheckConfigLimitCB: Object #####-###-####-####-##### has exceeded maximum number of components per object (2040).
2026-04-21T08:58:58.649Z Cr(26) clomd[2100902]: [Originator@########opID=########] CLOMStepFixObject: Fail component limit check for concat leg 0: Too many elements for list

Resolution

1. Identify the owner host for object affected. 

2. On the owner host, run the following command to enable recovery mode:

/usr/lib/vmware/vsan/bin/clom-tool enable-clom-recovery-mode -m 7 -u <OBJECT-UUID> 

3. Monitor /var/log/clomd.log for the following string to confirm the recovery task is complete:

CLOM_Recovery: exit: obj ######-####_####_########### configDelay 0 newConfigGenerated 1 recoveryMode RECOVER_ALL, recoveryEntity ######_#####_#####_######### status Success

4. Disable recovery mode

/usr/lib/vmware/vsan/bin/clom-tool enable-clom-recovery-mode -m 0

5. After running recovery mode, Verify the object no longer contains transient components.

 

6. Once all above is complete, Proceed to place the ESXi host into maintenance mode.

Powered by Wolken Software