On Tue, 2014-01-07 at 10:18 +0100, Nicolas Ecarnot wrote:
Le 07/01/2014 09:57, Nicolas Ecarnot a écrit :
Le 07/01/2014 09:02, Nicolas Ecarnot a écrit :
http://list-archives.org/2013/10/25/users-ovirt-org/vm-snapshot-delete-faile...
I've sent two mails altogether - here's the other one: http://lists.ovirt.org/pipermail/users/2013-November/017557.html. In December I upgraded to Ovirt 3.3.2. After the upgrade snapshots works, but I still have a few VMs with broken snapshots. I don't need these VMs, but I'm keeping them to eventually try to repair them (when someone helps and tells me how).
[...] In the URL I provided above, the op is able to lvchange -aey the device. In my case, though a lvmdiskscan + a lvs is showing me the LV, there is not device in /dev/{the proper VG}/{my missing LV}.
Although I couldn't see the device in /dev, activating it with lvchange -aey and providing the complete path lead to a successful activation of the LV.
Then, like in the URL above, I was able to run the VM manually from the host with a simple qemu-kvm.
But when trying to run it from oVirt, I still get the same errors, and the LV gets disabled.
What would be the best way now?
I have to add that in this precise case, recovering the VM is way more important than to recover the snapshot, that I can live without.
-- Milan Dlauhy ICZ a.s. Na hřebenech II 1718/10, 147 00 Praha 4 Nusle, CZ Tel.: +420 222 275 239 +420 724 429 878 Fax: +420 222 271 112 mailto:milan.dlauhy@i.cz http://www.i.cz midl@jabbim.cz, ICQ#344919380