[ https://issues.apache.org/jira/browse/CLOUDSTACK-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594507#comment-13594507 ]
Hongtu Zang commented on CLOUDSTACK-1531: ----------------------------------------- It happens in vmware only. we use the same code to handle both snapshot and template. The diffrent is in secondary storage, template has only 1 ova and ovf files, while snapshot has all ova in a same directory named by volume id. so, we will fetch the same ovf if we created a volume from a snapshot before, no matter how match snapshot created. A solution is making a directory for each snapshot. I fixed it in https://reviews.apache.org/r/9772/ > vmware create volume from snapshot will missing data > ---------------------------------------------------- > > Key: CLOUDSTACK-1531 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1531 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Snapshot, VMware > Affects Versions: 4.1.0 > Environment: esx5.0, management server in centos6.3, centos vm > Reporter: Hongtu Zang > Fix For: 4.1.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Reproduce: > 1. deploy a centos vm > 2. create a volume v0 and attached to the vm > 3. before formatting v0, take a snapshot s1, then format it and touch some > files > 4. take another snapshot s2, and detach v0 > 5. create volume v1 from s1 and then create volume v2 from s2 > 6. attach v1 and v2 to the vm respectively, we will find v1 and v2 are the > same volume, no partition in it. > if we create v2 first, we will find v1 and v2 has the same file we touched > before. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira