<div dir="ltr"><div>Does this report an error on the host where you are having problems activating logical volumes?</div><div><br></div><div> lvs -a -o +devices</div><div><br></div><div>Also, do the lvm commands succeed when you explicitly disable lvmetad, ie...</div><div><br></div><div> lvchange --config 'global {use_lvmetad=0}' -ay ...</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 20, 2017 at 3:38 AM, Nicolas Ecarnot <span dir="ltr"><<a href="mailto:nicolas@ecarnot.net" target="_blank">nicolas@ecarnot.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
I'm still coping with my qemu image corruption, and I'm following some Redhat guidelines that explains the way to go :<br>
- Start the VM<br>
- Identify the host<br>
- On this host, run the ps command to identify the disk image location :<br>
<br>
# ps ax|grep qemu-kvm|grep vm_name<br>
<br>
- Look for "-drive file=/rhev/data-center/0000000<wbr>1-0001-0001-0001-00000000033e/<wbr>b72773dc-c99c-472a-9548-<wbr>503c122baa0b/images/91bfb2b4-<wbr>5194-4ab3-90c8-3c172959f712/<wbr>e7174214-3c2b-4353-98fd-<wbr>2e504de72c75"<br>
(YMMV)<br>
<br>
- Resolve this symbolic link<br>
# ls -la /rhev/data-center/00000001-000<wbr>1-0001-0001-00000000033e/b7277<wbr>3dc-c99c-472a-9548-503c122baa0<wbr>b/images/91bfb2b4-5194-4ab3-<wbr>90c8-3c172959f712/e7174214-<wbr>3c2b-4353-98fd-2e504de72c75<br>
lrwxrwxrwx 1 vdsm kvm 78 3 oct. 2016 /rhev/data-center/00000001-000<wbr>1-0001-0001-00000000033e/b7277<wbr>3dc-c99c-472a-9548-503c122baa0<wbr>b/images/91bfb2b4-5194-4ab3-<wbr>90c8-3c172959f712/e7174214-<wbr>3c2b-4353-98fd-2e504de72c75 -> /dev/b72773dc-c99c-472a-9548-5<wbr>03c122baa0b/e7174214-3c2b-4353<wbr>-98fd-2e504de72c75<br>
<br>
- Shutdown the VM<br>
- On the SPM, activate the logical volume :<br>
# lvchange -ay /dev/b72773dc-c99c-472a-9548-5<wbr>03c122baa0b/e7174214-3c2b-4353<wbr>-98fd-2e504de72c75<br>
<br>
- Verify the state of the qemu image :<br>
# qemu-img check /dev/b72773dc-c99c-472a-9548-5<wbr>03c122baa0b/e7174214-3c2b-4353<wbr>-98fd-2e504de72c75<br>
<br>
- If needed, attempt a repair :<br>
# qemu-img check -r all /dev/...<br>
<br>
- In any case, deactivate the LV :<br>
# lvchange -an /dev/...<br>
<br>
<br>
I followed this steps tens of times, and finding the LV and activating it was obvious and successful.<br>
Since yesterday, I'm finding some VMs one which these steps are not working : I can identify the symbolic link, but the SPM neither the host are able to find the LV device, thus can not LV-activate it :<br>
<br>
# lvchange -ay /dev/de2fdaa0-6e09-4dd2-beeb-1<wbr>812318eb893/ce13d349-151e-4631<wbr>-b600-c42b82106a8d<br>
Failed to find logical volume "de2fdaa0-6e09-4dd2-beeb-18123<wbr>18eb893/ce13d349-151e-4631-<wbr>b600-c42b82106a8d"<br>
<br>
Either I need two more coffees, either I may be missing a step or something to check.<br>
Looking at the SPM /dev/disk/* structure, it looks like very sound (I can see my three storage domains dm-name-* series of links).<br>
<br>
As the VM can nicely be ran and stopped, does the host activates something more before being launched?<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Nicolas ECARNOT<br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Adam Litke</div></div>
</div>