Sangeetha Hariharan created CLOUDSTACK-5370: -----------------------------------------------
Summary: Xenserver - Snapshots - vhd entries get accumulated on the primary store when snapshot creation fails becasue of not being able to reach the secondary store. Key: CLOUDSTACK-5370 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5370 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Environment: Build from 4.3 Reporter: Sangeetha Hariharan Priority: Critical Fix For: 4.3.0 Set up: Advanced Zone with 2 Xenserver 6.2 hosts: 1. Deploy 5 Vms in each of the hosts with 10 GB ROOT volume size , so we start with 10 Vms. 2. Start concurrent snapshots for ROOT volumes of all the Vms. 3. Shutdown the Secondary storage server when the snapshots are in the progress. ( In my case i stopped the nfs server) 4. Bring the Secondary storage server up after 12 hours. ( In my case started the nfs server). When secondary server was down (NFS server down) for about 12 hours , I see that hourly snapshots get attempted every hour and fail with “CreatedOnPrimary" state . I see many entries being created on the primary store ( I see 120 entries , but I have only 14 vms). We accumulate 2 vhd files on the primary store for every snapshot that is attempted. When secondary store is brought up , and when another snapshot is attempted and it succeeds, we see the vhd files are all being cleared out. This is a problem that we accumulate so many vhd files ( In case of vmware and kvm where there are no delta snapshots this size would be significantly higher) on primary store. -- This message was sent by Atlassian JIRA (v6.1#6144)