You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Likitha Shetty (JIRA)" <ji...@apache.org> on 2014/06/26 10:53:26 UTC
[jira] [Resolved] (CLOUDSTACK-6224) VM Snapshot inconsistent size
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Likitha Shetty resolved CLOUDSTACK-6224.
----------------------------------------
Resolution: Fixed
Fix Version/s: 4.4.0
> 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)