[jira] [Assigned] (CLOUDSTACK-6224) VM Snapshot inconsistent size

["Rajani Karuturi (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajani Karuturi reassigned CLOUDSTACK-6224:
-------------------------------------------

    Assignee: Rajani Karuturi

> 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: Rajani Karuturi
>              Labels: snapshot, vmware, xen
>
> 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)