Thank you! and thank you!
I will make the correction.

Minor correction under RAID-5. I think the following sentence should say RAID-1 not RAID-0.

“After a failed drive is replaced, a rebuild cycle begins. As with the RAID-0, this can be a vulnerable time due to the uncommonly high I/O load. Many RAID-5 controllers also allow this to be throttled.”

Minor correction under RAID-5. I think the following sentence should say RAID-1 not RAID-0.

“After a failed drive is replaced, a rebuild cycle begins. As with the RAID-0, this can be a vulnerable time due to the uncommonly high I/O load. Many RAID-5 controllers also allow this to be throttled.”

I’ll say up front that I am by no means an expert on Storage Spaces. Storage Spaces is intended more for internal and direct-attached storage. I think there are ways to get it to work with a SAN but that’s not really its intended purpose.
When a SAN is present, my preference is to just have the nodes directly connect to it using CSV. There is the option of having one or more Windows Server systems in front of it presenting that storage as an SMB 3 share. That adds extra hardware and network hops, though, which translates to higher storage latency. The benefit would be that storage access would be controlled at the more familiar Windows layer and not on the hardware.