so whats happening, i believe, is we copy the base template to primary storage. we then create a linked clone (the smaller volume youre seeing), and use that for the guest vm. If you destroy that vm, the linked clone will go away. The base image will get cleaned up sooner or later, as long as there are no other vm's running that depend on it. The cleanup will eventually happen depending on how aggressively you setup your cleanup intervals.
On Tue, Feb 5, 2013 at 2:23 AM, Sunilreddy Kovvuri <sunil570....@gmail.com>wrote: > Hi all, > > Why the junk data of instance is not being deleted after the deletion of > instance > > Here is my test case > > My primary disk mount /mnt > > 1.Creating a template from snapshot > > size of /mnt before creating template:16068 MB > size of /mnt when creating template:25058 MB(on process) > size of /mnt after registering template:16068 MB > > 2.Registered a instance using the template > > *Before registering instance:*(size in MB) > > 38 0c9373ee-4c3c-40b3-9fe1-66c5c1c042f0 > 1352 2cb082d4-fe9a-4e65-b630-593f62fbb474 > 2831 3c9a2465-3320-4cb0-bc6e-cb6ee1e07a7e > 1 4bbadc87-d754-4c82-a29d-94fa627bcde2 > 27 5801fbc4-022c-423c-be5d-aa40d5a125e0 > 1497 5c2b2cec-bd31-45d6-9f4a-8d52e10f46b7 > 602 603fadf0-2ab6-477d-afaa-dca4cd254e5d > 656 68b6aec1-b5e9-4c08-9b0d-08131cd9b914 > 1 8ca4bcd6-0991-41fa-9293-24b29776c3bd > 43 944b1903-771b-4144-a74b-1f46b9332f4f > 51 add08a18-4354-4a54-9e90-9c4e4b6975b2 > 1 b090e998-fd41-4d35-9ada-6002515cf95d > 2724 c565ffde-7b11-418a-8ab2-441650fddcd1 > 3100 c97ce652-73ae-4a38-8e6e-d9eba553b8d5 > 1 d1209e83-9a16-4ff7-ba42-a97365a0e035 > 1497 e67ef89d-1d08-4806-92a3-83084913229b > 37 f23ad492-2eff-40a9-8cf4-c366b96c0d45 > 693 f27148a7-5a84-4ec4-8a38-82c983fb1832 > 1 fa568fe9-2dbe-4cd8-af13-2cea8224e74c > 1 KVMHA > 2 r-4-VM-patchdisk > 2 s-1-VM-patchdisk > 2 s-37-VM-patchdisk > 2 v-2-VM-patchdisk > 2 v-36-VM-patchdisk > > After registering instance one new file created,which is marked below.Size > of file 1497 MB i.e..,1.5 GB > > 38 0c9373ee-4c3c-40b3-9fe1-66c5c1c042f0 > 1352 2cb082d4-fe9a-4e65-b630-593f62fbb474 > 2831 3c9a2465-3320-4cb0-bc6e-cb6ee1e07a7e > 1 4bbadc87-d754-4c82-a29d-94fa627bcde2 > 27 5801fbc4-022c-423c-be5d-aa40d5a125e0 > 1497 5c2b2cec-bd31-45d6-9f4a-8d52e10f46b7 > 1497 603fadf0-2ab6-477d-afaa-dca4cd254e5d > 656 68b6aec1-b5e9-4c08-9b0d-08131cd9b914 > 1 8ca4bcd6-0991-41fa-9293-24b29776c3bd > 43 944b1903-771b-4144-a74b-1f46b9332f4f > 51 add08a18-4354-4a54-9e90-9c4e4b6975b2 > 1 b090e998-fd41-4d35-9ada-6002515cf95d > 2724 c565ffde-7b11-418a-8ab2-441650fddcd1 > 3100 c97ce652-73ae-4a38-8e6e-d9eba553b8d5 > 1 d1209e83-9a16-4ff7-ba42-a97365a0e035 > 1497 e67ef89d-1d08-4806-92a3-83084913229b > 1 f05800d7-eee9-479e-9ad9-95c907c2f8bd > 37 f23ad492-2eff-40a9-8cf4-c366b96c0d45 > 693 f27148a7-5a84-4ec4-8a38-82c983fb1832 > 1 fa568fe9-2dbe-4cd8-af13-2cea8224e74c > 1 KVMHA > 2 r-4-VM-patchdisk > 2 s-1-VM-patchdisk > 2 s-37-VM-patchdisk > 2 v-2-VM-patchdisk > 2 v-36-VM-patchdisk > > 3. Now,I had deleted the instance which i had registered.After deletion of > instance there is no much change in size (only 20 mb deleted) but > newly created file (1.5GB) is still existing > 1497 603fadf0-2ab6-477d-afaa-dca4cd254e5d > > 4. Now i registered new instance with same template.It created a new file > and its size is only 22MB.If i delete the instance the new file of > size22MB is deleted > > > Why is the flle size of 1.5 GB when i registered the instance for first > time is not being deleted from my storage >
