Sangeetha Hariharan created CLOUDSTACK-5809:
-----------------------------------------------
Summary: Not able to deploy Vm becasue of crossing
pool.storage.allocate d.capacity.disablethreshold even though the threshold has
not been reached in the primary store.
Key: CLOUDSTACK-5809
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5809
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.3.0
Environment: Build from 4.3
Reporter: Sangeetha Hariharan
Fix For: 4.3.0
Not able to deploy Vm because of crossing pool.storage.allocate
d.capacity.disablethreshold even though the threshold has not been reached in
the primary store.
Steps to reproduce the problem:
Xenserver set up with 2 Xensserver hosts:
In my case , Primary storage NFS has 222GB . (storage.overprovisioning.factor
is set to 2).
I tried to deploy 20 Vms with the same template that has Virtual size of 20.00
GB and actual size is about 10 GB.
I was allowed to deploy only 17 Vms after which Vm deployment fails because of
the following exception because of crossing pool.storage.allocate
d.capacity.disablethreshold :
2014-01-06 17:34:21,881 DEBUG [c.c.s.StorageManagerImpl]
(Job-Executor-32:ctx-2a944d7f ctx-6e9eaab0) Checking pool 1 for storage,
totalSize: 2
37777190912, usedBytes: 88645566464, usedPct: 0.3728093772325169, disable
threshold: 0.85
2014-01-06 17:34:21,885 DEBUG [c.c.s.StorageManagerImpl]
(Job-Executor-32:ctx-2a944d7f ctx-6e9eaab0) Checking pool: 1 for volume
allocation [V
ol[24|vm=24|ROOT]], maxSize : 475554381824, totalAllocatedSize : 394411376640,
askingSize : 21474836480, allocated disable threshold: 0.85
2014-01-06 17:34:21,886 DEBUG [c.c.s.StorageManagerImpl]
(Job-Executor-32:ctx-2a944d7f ctx-6e9eaab0) Insufficient un-allocated capacity
on: 1
for volume allocation: [Vol[24|vm=24|ROOT]] since its allocated percentage:
0.8745292421128761 has crossed the allocated pool.storage.allocate
d.capacity.disablethreshold: 0.85, skipping this pool
Since Xenserver uses thin provisioning , the base copy of the template in
primary is 10 GB. All the vhd entries of the Vms are very small and point to
the base copy. We need to allocate only 10 GB space ( 20 GB (virtual size of
template) - 10 gb ( actual size of tenplate) for each of these Vms , in
addition to 10 GB for the base template copy.
But we are allocating 20 GB for each of the Vms deployed.
Reported Primary Storage capacity - 82 % - 367.32 GB / 442.89 GB
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
