[
https://issues.apache.org/jira/browse/CLOUDSTACK-8896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865422#comment-15865422
]
ASF subversion and git services commented on CLOUDSTACK-8896:
-------------------------------------------------------------
Commit 2aeca0d34fc1e7352a9a287b965202cdd1a7f6a5 in cloudstack's branch
refs/heads/master from [~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2aeca0d ]
Merge release branch 4.9 to master
* 4.9:
CLOUDSTACK-8896: allocated percentage of storage pool going beyond 100%
> Allocated percentage of storage can go beyond 100%
> --------------------------------------------------
>
> Key: CLOUDSTACK-8896
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8896
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.5.2, 4.6.0
> Reporter: Rajani Karuturi
> Assignee: Rajani Karuturi
>
> This issue occurs when a volume in Ready state is moved across storage pools.
> Let us say there is a data volume, volume0 in Ready state in a cluster scope
> primary storage primary0.
> Now, when an operation is attempted to attach this volume to a vm in another
> cluster, the volume is moved to the new cluster and the asking size is zero
> at this time.
> you can observe logs like below with asking size 0 in the management server
> logs.
> 2015-09-22 08:49:02,754 DEBUG [c.c.s.StorageManagerImpl]
> (Work-Job-Executor-6:ctx-27e0990a job-37/job-38 ctx-985e5ad0)
> (logid:a0a97129) Checking pool: 1 for volume allocation
> [Vol[8|vm=null|DATADISK]], maxSize : 3298534883328, totalAllocatedSize :
> 24096276480, askingSize : 0, allocated disable threshold: 0.85
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
