StarWind Software

Am I just dumb? I have a 705GB vDisk created on my Windows 2012 server out of my Storage Spaces Storage Pool. I attempt to create a device in Starwind v8 Beta and point it at P: (where the vDisk is mounted) and try to create a 700GB thick provisioned virtual disk.

"Not enough disk space."

OK, how about 699GB? No. 690GB? No. 600GB? No. 100GB? That works. WTF?

Is thick provisioned virtual disks broken?

I assume the P: volume is a newly created and blank one and it definitely has enough free space.
OK, let me check that in our testlab.

Figured it out.

Even though I was telling the new virtual disk to go to P:\, Starwind had a default Storage Pool entry of C:\Storage and was attempting to put the new device there rather than P:\.

After I changed the default Storage Pool location to P:\ then I could create the thick provisioned virtual disk and create a device. Looks like I'll have to change that default every time I provision a virtual disk if I want it in a different location.

Well, the obvious reasons are the most hard to find

Anyway, we are glad that you are all set now,

Is that normal that I should have to change the default storage pool every time I create a device? I'd think setting a custom path at device creation would override the default.

No it's not. We'll file a bug.

turkina wrote:Is that normal that I should have to change the default storage pool every time I create a device? I'd think setting a custom path at device creation would override the default.

Update. Bug is fixed. Beta-2 will be free from it. Stay tuned!