[
https://issues.apache.org/jira/browse/CLOUDSTACK-6224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044479#comment-14044479
]
Likitha Shetty commented on CLOUDSTACK-6224:
--------------------------------------------
Mike, looks like the fix made for
[https://issues.apache.org/jira/browse/CLOUDSTACK-6488] will take care of this
issue.
With [https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=54c0df5], in
4.4 we search for the VMDK name (for e.g. ROOT-1) and not just keyword 'ROOT'
in the datastore while retrieving the size of the snapshot chain for a volume.
And since the VMDK name is unique for a volume we will only add up the sizes of
the files associated with that volume.
Tested to confirm it resolves the issue.
> VM Snapshot inconsistent size
> -----------------------------
>
> Key: CLOUDSTACK-6224
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6224
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller, Management Server
> Affects Versions: 4.2.1
> Environment: Cloudstack 4.2.1
> XenServer 6.2
> Vcenter 5.5 ESXi
> Reporter: Artjoms Petrovs
> Assignee: Mike Tutkowski
> Labels: snapshot, vmware, xen
> Fix For: 4.4.0
>
>
> During the creation of VM Snapshot [VMware], resulting size is written in
> table „volumes”, column vm_snapshot_chain_size. It seems that size of a VM
> Snapshot is calculated manually via the method getVMSnapshotChainSize(..)
> and it gives overexpected result ( hundreds of terabytes ) and is much larger
> than the filesize, that we can see in VMware itself. By calculating the vmdk
> and vmsn file sizes manually. Xen VM snapshots [disks only] give similar
> results. For me it seems that either the method works incorrectly, either it
> loops between some simlinks.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
