I think we all know about the NumberOfColumns issues: https://blogs.technet.microsoft.com/tip_of_the_day/2015/03/17/tip-of-the-day-numberofcolumns/
That said, let's pretend to plan the following (at home, not enterprise):
- create a 2 disk stripe (simple storage spaces)
- be able to add another SINGLE disk later
Therefore we create a pool with a single disk and create the virtual disk afterwards. Now, we forced Windows to create the vdisk with NumberOfColumns = 1. Then we add the second disk to the pool and extend the vdisk. Works great.
NumberOfColumns is still 1 because this was set when we created the vdisk in the first place. Months later we could add another single disk and extend the vdisk. Gotcha! We do not need to add at least 2 drives each time we want to extend disk space.
My question now: Is there any bad impact of using NumberOfColumns = 1? Because if you look at the picture in the article above, data is now written into just "1 column". The 3 disks are like "3 rows" instead of one row and 3 columns. But, does this matter? In terms of speed for example? Or manageability?
Thanks!