GitHub user DaanHoogland added a comment to the discussion: Not able to deploy VM: Insufficient un-allocated capacity on StoragePool
> I tested with a thin disk service offering and Overprovisioning factor=1 on > primary storage and got the same error when allocating the space for the VM @mbertolina this sounds like a way to hit the limit sooner, rather than later. If thin provisioning, it will not occupy the space completely from the start, but it will mark it as allocated. thin provisioning and overprovisioning work together to help you make good use of your disk space. If say half your disks are thin provisioned and they take about 10% of the space you need and the other half are thick provisioned, you would want 0.5*0.1 + 0.5 times the physical space to be able to allocate all. You would then use 5+0.5 times the space you actually have to be allocatable. Rounding down for safety of course. Also keep in mind life-spans of VMs, are they expected to grow to their full size during their life-time or will they be recycled when half way through their space. I wrote this while @weizhouapache replied. We are saying basically the same thing but in slightly different ways. Please ask more questions or if you understand help us improve the documentation at https://github.co m/apache/cloudstack-documentation GitHub link: https://github.com/apache/cloudstack/discussions/14045#discussioncomment-18268625 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
