<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Sun, Aug 14, 2016 at 8:07 PM Nir Soffer <<a href="mailto:nsoffer@redhat.com">nsoffer@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sun, Aug 14, 2016 at 5:55 PM, Siavash Safi <<a href="mailto:siavash.safi@gmail.com" target="_blank">siavash.safi@gmail.com</a>> wrote:<br>
> Hi,<br>
><br>
> An unknown bug broke our gluster storage (dom_md/ids is corrupted) and oVirt<br>
> no longer activates the storage(I tried to recover it using the similar<br>
> issues reported in mailing list but it didn't work).<br>
<br>
Can you explain what you did?<br></blockquote><div>cd /mnt/4697fbde-45fb-4f91-ac4c-5516bc59f683/dom_md/</div><div>rm ids</div><div>touch ids</div><div><span style="line-height:1.5">sanlock direct init -s 4697fbde-45fb-4f91-ac4c-5516bc59f683:0:ids:1048576</span><span style="line-height:1.5"> </span><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The best way to fix this is to initialize the corrupt id file and<br>
activate the domain.</blockquote><div>This would be great! </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span style="line-height:1.5"> </span><br></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> As I checked VM disk images are still accessible when I mount the gluster<br>
> storage manually.<br>
> How can we manually move the VM disk images to local storage? (oVirt<br>
> complains about gluster storage being inactive when using the web interface<br>
> for move/copy)<br>
<br>
You can easily copy the images to another file based storage (nfs,<br>
gluster) like this:<br>
<br>
1. activate other storage domain using engine<br>
2. mount gluster domain manually<br>
3. copy the image from gluster domain to the other domain:<br>
<br>
cp -r gluster-domain-mountpoint/images/image-uuid<br>
/rhev/data-center/mnt/server:_path/other-domain-uuid/images/<br>
<br>
But the images will not be available since engine does know them.<br>
Maybe this can be<br>
fixed by modifying engine database.<br>
<br></blockquote><div>How complicated is it?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Another solution (if you are using ovirt 4.0), is to upload the images<br>
to a new disk,<br>
and attach the disk to the vm instead of the missing disk.</blockquote><div>We are running 3.6</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span style="line-height:1.5"> </span><br></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Nir<br>
</blockquote></div></div>