VSAN default storage policy (FTT=1): large disks get stripped?!

[jkoebrunner]

What I have found out while ivestigating a VSAN resync problems, is that two VMs have vdisks which are striped into more objects.

This is strange because the default storage policy only defines FTT=1.

It's strange that there are RAID1, RAID0, RAID1 objects with the default policy as seen in the screenshot attached.

I assume that is somehow related to the size of the vdisks. I have also checked that wihth another VSAN installation, there its also the same.

Can somebody tell me at which size VSAN decides to stripe vdisk objects?

BR Johannes

[CHogan · Accepted solution]

This should help to explain it - VSAN Part 23 – Why is my Storage Object Striped? | CormacHogan.com

[jkoebrunner]

Thanks for your fast and plausible answer

Anyhow, it's a little bit strange that there is a RAID1 in a RAID0 as seen on the screenshot?

Can you explain this behaviour?

[CHogan]

It might be because it is reconfiguring (not sure).

Check it again when everything is synced and active.

[jkoebrunner]

This state exists now for 24 hours and vdisks are partly inaccessible.

vsan.resync_dashboard does not show any resync in progress...

vsan.check_state reports missing objects...

We have a Webex session with Vmware support soon...