This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We are using Storage Spaces on a VMware server, running Windows Server 2019. We didn't need anything fancy like parity or mirroring since the 'disks' in question are all virtual, VMDK files that VMware manages. The only reason I wanted to use Storage Spaces was for its JBOD functionality; VMDK files have a maximum file size of 64TB which I felt like my file server will run up against in the next few years (it's already at 30TB). So I thought, storage spaces will let me add an additional disk to it in the future, and seamlessly add that new disk to the Pool, so that it will look - to my users - like their network drives has just grown larger than 64TB.
But I'm not at that point yet - I merely wanted to expand the size of my vdisk (and therefore pool and volume) from 35TB to 45TB.
No problems on the VMWare size - expanding the VMDK from 30 -> 40TB went perfectly. I've done this hundreds of times without issues. But this is my first time using Storage Spaces with a VMDK file because this is our largest volume we provide to our users, by far.
The problem arose in Windows Server - I cannot get Windows to recognize that the underlying "physical disk" is no longer 30TB, but instead 40TB. I have tried in Disk Management simple refresh, and rescan storage.
I do know that when you try to add additional DISKS to storage spaces, you need to add a number of drives equal to the NumberOfColumns field. My "NumberOfColumns" is 1 in this case. But does that even matter? I'm not trying to add more disks/drives at this time, I'm merely trying to get Windows to see that the underlying physical disk is now a larger size than it was before, so I can use the "extend virtual disk" function to make the virtual disk "Project-Disk" larger.
Do I need to reboot for Windows to recognize the new physical size of the "VMware virtual disk"? I can do that next month, but I can't do it now because this is our main production file server.
Would love to get the advice of some Storage Spaces experts.