I've had to pick up a problem with a MD3200 unit connected to two R620 PEs running ESXi/ vSphere via SAS HBAs.
There is a single disk pool configured with two Virtual Disks, with virtual capacities of 200GB and ~3TB.
This is the General VD:
Looking at the thin provisioning settings seemed to indicate it had reached a capacity limit around 500GB and couldn't expand.
Thus, for this VD, I went into Change > Repository Settings and changed the value for Repository Expansion Policy to be as shown here:
So the information for the VD now shows this information:
So does this mean this VD can now grow up to 1024GB as needed?
If so, will it jump from the current capacity of 528GB to 1024GB in a single increment? Or grow in blocks?
I'm concerned that I haven't changed the right settings, so when the 3% free capacity is used the VD won't grow and the guest VMs in vSphere will have problems again. If I right click the VD and choose "Increase Repository Capacity", increasing the capacity change by any value (eg 4GB) returns an error 675 (... the expansion policy specified is not valid). I presume this is because the VD is set with an automatic expansion policy to go to 1024GB?
Finally, when setting the Repository Expansion Policy, the help text says you can enter a value of 64.000TB to disable the limit on physical capacity. How does that link with the virtual capacity allocated to the VD (3072GB)? Does that simply mean the Repository will grow as big as the VD virtual capacity limit of ~3TB?
Thanks,
Chris.