Created attachment 648488 [details] logs and screen shot Description of problem: I ran a vm with thin provision disk and moved the disk several times from one domain to another domain. disk size is reported as 15GB size and 16GB actual size. after I shut down the vm and deleted all the live image migration snapshots the disk is reported as 15GB size and 3Gb actual size. looking at lvs the disk is reported as 16.62GB i moved the disk again, but this time while vm is down and the image size report changed to the actual size reported in lvs (15 size 17GB actual size). Version-Release number of selected component (if applicable): si24.2 How reproducible: 100% Steps to Reproduce: 1. create and run a vm with 15GB thin provision disk 2. move the disk 6 times -> look at the size reported in lvs and in UI 3. shut down the vm -> delete all snapshots -> look at the size reported by lvs and the UI 4. move the disk while vm is down -> look at the size reported by lvs and by UI Actual results: after we delete the snapshot the size reported by UI is not the lvs size when we move the disk when vm is down the actual size changed to the full siz of the lv Expected results: 1. we should report correct size 2. not for UI but - should image grow after the live migration with the full size of each snapshot merged? Additional info:logs and screen shots
(In reply to comment #0) > 2. not for UI but - should image grow after the live migration with the full > size of each snapshot merged? This is a another BZ if I understand correctly, and may be the more important then the two.
blocked by https://bugzilla.redhat.com/show_bug.cgi?id=913253
also blocked by https://bugzilla.redhat.com/show_bug.cgi?id=903248
tested on sf9 with vdsm-4.10.2-10.0.el6ev.x86_64 and scratch build of libvirt: libvirt-0.10.2-18.el6_4.eblake.2.x86_64 which is solving bug 903248 logs and screen shots will be attached below we can see that the image size in lvm is still large and UI is reporting after we removed the live migrate snapshots that the image is 15V size and 3G Actual size [root@gold-vdsc ~]# lvs LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert ids 2a333b65-68f8-4bb7-a74f-ddae3dbd0dfa -wi-ao--- 128.00m inbox 2a333b65-68f8-4bb7-a74f-ddae3dbd0dfa -wi-a---- 128.00m leases 2a333b65-68f8-4bb7-a74f-ddae3dbd0dfa -wi-a---- 2.00g master 2a333b65-68f8-4bb7-a74f-ddae3dbd0dfa -wi-a---- 1.00g metadata 2a333b65-68f8-4bb7-a74f-ddae3dbd0dfa -wi-a---- 512.00m outbox 2a333b65-68f8-4bb7-a74f-ddae3dbd0dfa -wi-a---- 128.00m 4828bea2-2686-4462-b65f-8970b0fe6d9d 52e4917b-10bc-4b03-9b82-a2e15732c15b -wi------ 16.62g ids 52e4917b-10bc-4b03-9b82-a2e15732c15b -wi-ao--- 128.00m inbox 52e4917b-10bc-4b03-9b82-a2e15732c15b -wi-a---- 128.00m leases 52e4917b-10bc-4b03-9b82-a2e15732c15b -wi-a---- 2.00g master 52e4917b-10bc-4b03-9b82-a2e15732c15b -wi-a---- 1.00g metadata 52e4917b-10bc-4b03-9b82-a2e15732c15b -wi-a---- 512.00m outbox 52e4917b-10bc-4b03-9b82-a2e15732c15b -wi-a---- 128.00m ids 964a332f-64e4-43cf-9c04-d581a21f0ad2 -wi-ao--- 128.00m inbox 964a332f-64e4-43cf-9c04-d581a21f0ad2 -wi-a---- 128.00m leases 964a332f-64e4-43cf-9c04-d581a21f0ad2 -wi-a---- 2.00g master 964a332f-64e4-43cf-9c04-d581a21f0ad2 -wi-a---- 1.00g metadata 964a332f-64e4-43cf-9c04-d581a21f0ad2 -wi-a---- 512.00m outbox 964a332f-64e4-43cf-9c04-d581a21f0ad2 -wi-a---- 128.00m lv_home vg0 -wi-ao--- 101.08g lv_root vg0 -wi-ao--- 19.53g lv_swap vg0 -wi-ao--- 15.62g
Created attachment 705489 [details] logs and screen shots
(In reply to comment #7) > tested on sf9 with vdsm-4.10.2-10.0.el6ev.x86_64 and scratch build of > libvirt: libvirt-0.10.2-18.el6_4.eblake.2.x86_64 which is solving bug 903248 > > logs and screen shots will be attached > > below we can see that the image size in lvm is still large and UI is > reporting after we removed the live migrate snapshots that the image is 15V > size and 3G Actual size > > [root@gold-vdsc ~]# lvs > LV VG > Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert > ids 2a333b65-68f8-4bb7-a74f-ddae3dbd0dfa > -wi-ao--- 128.00m > inbox 2a333b65-68f8-4bb7-a74f-ddae3dbd0dfa > -wi-a---- 128.00m > leases 2a333b65-68f8-4bb7-a74f-ddae3dbd0dfa > -wi-a---- 2.00g > master 2a333b65-68f8-4bb7-a74f-ddae3dbd0dfa > -wi-a---- 1.00g > metadata 2a333b65-68f8-4bb7-a74f-ddae3dbd0dfa > -wi-a---- 512.00m > outbox 2a333b65-68f8-4bb7-a74f-ddae3dbd0dfa > -wi-a---- 128.00m > 4828bea2-2686-4462-b65f-8970b0fe6d9d 52e4917b-10bc-4b03-9b82-a2e15732c15b > -wi------ 16.62g > ids 52e4917b-10bc-4b03-9b82-a2e15732c15b > -wi-ao--- 128.00m > inbox 52e4917b-10bc-4b03-9b82-a2e15732c15b > -wi-a---- 128.00m > leases 52e4917b-10bc-4b03-9b82-a2e15732c15b > -wi-a---- 2.00g > master 52e4917b-10bc-4b03-9b82-a2e15732c15b > -wi-a---- 1.00g > metadata 52e4917b-10bc-4b03-9b82-a2e15732c15b > -wi-a---- 512.00m > outbox 52e4917b-10bc-4b03-9b82-a2e15732c15b > -wi-a---- 128.00m > ids 964a332f-64e4-43cf-9c04-d581a21f0ad2 > -wi-ao--- 128.00m > inbox 964a332f-64e4-43cf-9c04-d581a21f0ad2 > -wi-a---- 128.00m > leases 964a332f-64e4-43cf-9c04-d581a21f0ad2 > -wi-a---- 2.00g > master 964a332f-64e4-43cf-9c04-d581a21f0ad2 > -wi-a---- 1.00g > metadata 964a332f-64e4-43cf-9c04-d581a21f0ad2 > -wi-a---- 512.00m > outbox 964a332f-64e4-43cf-9c04-d581a21f0ad2 > -wi-a---- 128.00m > lv_home vg0 > -wi-ao--- 101.08g > lv_root vg0 > -wi-ao--- 19.53g > lv_swap vg0 > -wi-ao--- 15.62g The underlying issue in the described scenario is live snapshot step. When removing a snapshot that was created during live snapshot process, the image(s) new size is not updated in the DB. I.e. Image's size should be fetched using GetImageInfo and updated in the DB after snapshot merge operation. A new blocking bug should be opened for it.
Bug 923864 has been opened on the issue.
bug verification is depending on Bug 923864
sf15. verified. tested according steps to reproduce. UI shows the size of 17 GB. [root@purple-vds3 ~]# lvs LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert d75eb141-f124-46c2-829b-33d18f2efaaa 45a072b8-8377-482e-bcad-5192d235ae0d -wi------ 16.62g ids 45a072b8-8377-482e-bcad-5192d235ae0d -wi-ao--- 128.00m inbox 45a072b8-8377-482e-bcad-5192d235ae0d -wi-a---- 128.00m leases 45a072b8-8377-482e-bcad-5192d235ae0d -wi-a---- 2.00g master 45a072b8-8377-482e-bcad-5192d235ae0d -wi-a---- 1.00g metadata 45a072b8-8377-482e-bcad-5192d235ae0d -wi-a---- 512.00m outbox 45a072b8-8377-482e-bcad-5192d235ae0d -wi-a---- 128.00m 03a3dd0c-0300-47ef-9de0-d08cc1bee71c d9f9688f-9355-4be9-bf23-f084602a6ded -wi-a---- 1.00g ids d9f9688f-9355-4be9-bf23-f084602a6ded -wi-ao--- 128.00m inbox d9f9688f-9355-4be9-bf23-f084602a6ded -wi-a---- 128.00m leases d9f9688f-9355-4be9-bf23-f084602a6ded -wi-a---- 2.00g master d9f9688f-9355-4be9-bf23-f084602a6ded -wi-ao--- 1.00g metadata d9f9688f-9355-4be9-bf23-f084602a6ded -wi-a---- 512.00m outbox d9f9688f-9355-4be9-bf23-f084602a6ded -wi-a---- 128.00m lv_root vg0 -wi-ao--- 70.33g lv_swap vg0 -wi-ao--- 3.88g
3.2 has been released