efpbe
Contributor
Contributor
‎10-07-2023 02:06 AM

change space efficiency (DD/C to C) fails

Hi everyone

 

On one of our environments, we have to go back to compression only due to performance recommendations :

efpbe_1-1696669200621.png

 

We checked if everything was correct in terms of space, policies and health of each of the esxi but for some unknown reason, the conversion fails at 10% : General vSAN error. Resource check failed - Internal failure happened during the resource check. Please check clomd.log

 

On the host in question, we've checked the clomd.log (in attachments) and the only error I see is the multiple values like this : CLOMDecom_ComponentNeedsEvac: Could not find disk 00000000-0000-0000-0000-000000000000

 

But i'm not sure is this is the problem relative to the situation.

 

Any help is appreciated.

clomd.log
Reply
0 Kudos
TheBobkin
Champion
Champion
‎10-07-2023 08:57 AM

@efpbe, Can you please share the layout/policy of this object '5047d264-da13-bbf6-bb93-84160c080880'? Maybe it has a dedupe&compression-only policy:

esxcli vsan debug object list -u 5047d264-da13-bbf6-bb93-84160c080880

 

2023-10-07T08:26:57.657Z No(29) clomd[38181686]: [Originator@6876] CLOMWhatIfRecordResourceAndReplicas: targetPolicy: UFT1/LFT0, capacity-pref=0, currentPolicy: UFT1/LFT0, capacity-pref=0, item.origObjectAddressSpace=10700718080, targetAddress(totalComponentAddressSpace)=10700718080
2023-10-07T08:26:57.658Z No(29) clomd[38181686]: [Originator@6876] CLOM_CheckClusterResourcesForPolicy: Target datastore space efficiency policy is not compatible with current cluster configuration. DedupAndCompression:1, CompressionOnly:0, None:0
2023-10-07T08:26:57.658Z No(29) clomd[38181686]: [Originator@6876] CLOMWhatIfObjectDecom: Couldn't check cluster resources: Failure
2023-10-07T08:26:57.658Z No(29) clomd[38181686]: [Originator@6876] CLOMWhatIfRunDecom: Failed to decommission object 5047d264-da13-bbf6-bb93-84160c080880: Failure, doDeltaDecom = 0.

 

Reply
0 Kudos
efpbe
Contributor
Contributor
‎10-09-2023 05:37 PM

Yes, you're right !

efpbe_0-1696897700424.png

 

I think it's because the vSAN Default Storage Policy was in this status :

efpbe_1-1696897743747.png

 

but, when I put the cluster to "Compression only" and change the default policy to "Compression only" also, i've this error :

efpbe_2-1696897806313.png

 

I'm not aware of wich best practices must I follow to migrate from deduplication&compression to compression only :confused_face:

Reply
0 Kudos
TheBobkin
Champion
Champion
‎10-11-2023 12:17 PM

@efpbe, Are you sure that is the 'vSAN Default Storage Policy' applied to that object?(I think it is possible to still have multiple of these in SPBM inventory)

 

Asking as that object does not have 'No preference' rule on it - you should change it to 'No preference', apply it to all objects and validate this (from 'esxli vsan debug object list --all' output) has been applied to everything (not just what is registered in inventory!) that has 'Dedup&Compression' rule, then you should be able to reformat to Compression only (and change policy to that also, but not mandatory).

Reply
0 Kudos