Closed GreyKat closed 6 years ago
Awesome, thanks! Can you pease submit a pull request I can merge straight away? If not I will do it myself :)
Just add it yourself ;)
And thanks for this great tool!
Hi,
Le 28 juil. 2016 à 17:08, GreyKat notifications@github.com a écrit :
Just add it yourself ;)
And thanks for this great tool!
Yes thanks very much!
NM
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
You are welcome! Unfortunately there is a problem with tests as the libvirt "hack" doesn't work anymore. I will look into this asap, meanwhile if you are need the updated version you can clone the bugfix/deleting-old-bf branch
@GreyKat
1) Nice catch!
2) You said the function "get_backing_file" is called after consolidation. However the function get_backing_file IS called before consolidation on line 425. Consolidation doesn't start until line 429. I think you meant the function "get_snapshot_chain"
@dguerri Testing manually was ok except for one time when I ran into this issue ( https://bugzilla.redhat.com/show_bug.cgi?id=1197592 ) using blockcommit and running virsh version 1.3.1 and qemu-img version 2.5.0 (standards on Ubuntu 16.04.1 as of this date). I've not debugged it further because it doesn't happen 100% of the time and I'm time limited for the next few weeks. So This is just a side note for future tests: In theory, if the above libvirt race condition bug occurs again, the consolidation command should bomb out and stop the script before the deletes happen. Should confirm though. Just to be clear this is not a fi-backup.sh bug, but a core issue with libvirt.
@AJRepo Yep, you are right, it was a typo (bad copy/paste). The function is get_snapshot_chain
And it is running: CentOS Linux release 7.2.1511 (Core) 3.10.0-327.18.2.el7.x86_64 libVirt version '1.2.17' support is experimental QEMU/KVM version '2.0.0,' is supported
This is now working - closing.
Function get_snapshot_chain is called after consolidation, so it returns just current image of VM. The following fix works for me: