GitHub user nickaccuweb added a comment to the discussion: Not able to deploy VM: Insufficient un-allocated capacity on StoragePool
@mbertolina Thanks for sharing the CLVM_NG logs. In this case, increasing the storage overprovisioning factor will not help in the same way it did with the SharedMountPoint storage. >From the logs, CloudStack is calculating the storage like this: - Pool capacity: 4 TB - Already allocated: about 1.87 TB - New root disk requested: about 1.87 TB - Projected allocation: about 93.36% Your current pool.storage.allocated.capacity.disablethreshold is set to 0.85, so CloudStack stops the deployment once the calculated allocation goes above 85%. As a workaround, I would suggest increasing this setting to 0.95 for the affected storage pool instead of changing it globally. After changing it, please retry the VM deployment. The calculated 93.36% should then be within the allowed limit. Also, please keep monitoring the actual free space on the CLVM_NG/LVM storage, since increasing the threshold reduces the safety margin before the physical storage becomes full. One more thing: could you please confirm the exact CloudStack version currently running in this environment? Your earlier post mentioned 4.22.1.0, while CLVM_NG is associated with the newer CloudStack releases. Please let me know the result after changing the pool-specific threshold. GitHub link: https://github.com/apache/cloudstack/discussions/14045#discussioncomment-18445702 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
