mbertolina commented on issue #14031:
URL: https://github.com/apache/cloudstack/issues/14031#issuecomment-5500997468
Although changing parameter this may cause the VM to deploy, it is not the
expected result, and besides that, I want the calculated space not to exceed
the size of the primary storage disk (x1.0).
The problem is not the overprovisioning factor, it is how the available
space is calculated, when allocating 1.9T root disk from template (details
above) on an empty 4 TB primary storage (reporting: Disk Size (in GB): 4095.5
GB (x1.0), 0.05% Used,
0.00% Allocated)
Why: totalAllocatedSize : (1.8672 TB) 2052994367488 ? is it using "template
size" for this calculation instead of the physical size of the qcow2 file which
is "Template physical size: 20.81 GB"?
`2026-09-01 16:08:27,820 DEBUG [c.c.s.StorageManagerImpl]
(API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67)
Checking pool: StoragePool
{"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"}
for storage allocation , maxSize : (3.9995 TB) 4397514358784,
totalAllocatedSize : (1.8672 TB) 2052994367488, askingSize : (1.8672 TB)
2052994367488, allocated disable threshold: 0.85`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
