Dear France,
It is more than 6 months I have used vhd-util, and xe to clean-up
manually, but I remember that if you try to destroy VDI that has a child
- you'll get an error. Since you have all the chain from the parent you
should start from the last child and move to the top. You shouldn't be
able to destroy VDI in the middle of the chain, since it will definitely
corrupt data.
I didn't understand how exactly did you check existing VHD files?
How do you know it is corrupted? Does vhd-util query shows that? What
does it mean - "corrupted and not found". If it is not found, how do you
know it is corrupted?
Try to work with vhd-util -- it is great. I think you can resolve
all the issues with it.
Vadim.
On 2015-12-09 20:39, France wrote:
Thank you Vladim, for your response.
Ity is greatly appreciated.
I will surely read the document.
So If I understand correctly, I can try to remove it and if it would be
bad for my setup, xe will not do it? :-)
I guess coalesce will not work, if one VHD in chain is corrupted.
I guess I will have to try and repair it first.
We will see. :-)
I vageuly remember that thin provisioning was not possible with CLVM
over ISCSI at the time of cluster setup, so I guess we do not have it.
Regards,
F.
On 09 Dec 2015, at 18:18, Vadim Kimlaychuk <va...@kickcloud.net> wrote:
Dear France,
Hope this article helps you:
http://support.citrix.com/filedownload/CTX122978/XenServer_Understanding_Snapshots.pdf
[1] Common practice is to use "vhd-util" to merge (coalesce) VHD files
into usable image. Luckily xe tool is smart enough not to allow you
destroy image that is a part of the chain. Of course it is more safe to
copy all the files before destruction (in a case you have thin
provisioning).
Vadim.
On 2015-12-09 18:27, France wrote:
Hi guys,
below is the chain cross referenced with CS MySql database.
Can I delete/destroy 1a240d45-ee0a-4c30-809b-3114dfaf85ba without bad
consequences? Are next in chain dependant upon it?
*555b38bf[VHD](20.000G//2.695G|n) -> not foud
5afd5849[VHD](20.000G//8.000M|n) -> found in template_spool_ref. status
ready, template ID 292
*02e8b56b[VHD](20.000G//12.000M|n) -> not found
*1a240d45[VHD](20.000G//136.000M|n) <- corrupted and not found
*c99e711b[VHD](20.000G//136.000M|n) -> not found
34a03c9a[VHD](20.000G//8.000M|a) -> found in shapshot_store_ref. state
destroyed, volume id 661, from template id 292
5c12db0a[VHD](20.000G//8.000M|n) -> found in shapshot_store_ref. state
destroyed -> probably not part of the above chain?
I would do xe vdi-destroy=1a240d45-ee0a-4c30-809b-3114dfaf85ba .
Alternatively I think about exporting template ID 292 in CS, deleting
it and importing it back again. It should remove the whole chain,
right? 'Cause noone is using it?
Regards,
F.
Links:
------
[1]
http://support.citrix.com/filedownload/CTX122978/XenServer_Understanding_Snapshots.pdf
