<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Sure that ovirt is not directly concerned but this has been done
following the foreman integration feature. So a warning doing this
in a fc environnement could be very preventive.<br>
My question was rather : now is there a possibility to recover this
disk? After all, it is only a LVM disk with one VG per LUN and as
much LV as much as existing VMs. Recovering LVM metadata might be
enough?<br>
<br>
<div class="moz-cite-prefix">Le 21/06/2015 20:23, Dan Yasny a
écrit :<br>
</div>
<blockquote
cite="mid:CALLXwb6H_apELuw=h+uRA9er_Mn15Kw-46f=Fx5VsGoTSdyJ6w@mail.gmail.com"
type="cite">
<p dir="ltr">Anaconda and Kickstart are dangerous in FC
environments and have been known to wipe all kinds of data if
zoning wasn't properly done prior to os deployment to new hosts.
</p>
<p dir="ltr">Nothing to do with oVirt, it's a common mistake
people make at least once before they step on this specific
rake.</p>
<div class="gmail_quote">On Jun 21, 2015 2:09 PM, "Nathanaël
Blanchet" <<a moz-do-not-send="true"
href="mailto:blanchet@abes.fr">blanchet@abes.fr</a>> wrote:<br
type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">In a
traditional installation of an ovirt host, it seems that
provisionning the OS is the first step before talking about
vdsm. I didn't go further, the problem is that this host saw
the production LUN and the kickstart took all the lun into the
same VG with a XFS format.<br>
Yes it is an error from myself for not having dissociated the
lun.<br>
Yes it is an error from myself for not having taken care of
having snapshot lun level backup.<br>
But now what should I do?<br>
My idea was to use pvreduce to unlabel the LUN, and then using
the /etc/lvm/backup/lun for recovering physical volume
metadata on that lun (<a moz-do-not-send="true"
href="http://www.tldp.org/HOWTO/LVM-HOWTO/recovermetadata.html"
rel="noreferrer" target="_blank">http://www.tldp.org/HOWTO/LVM-HOWTO/recovermetadata.html</a>)<br>
<br>
Le 21/06/2015 12:02, mots a écrit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Let me get this straight:<br>
<br>
You added a new host and instead of letting VDSM manage the
VM storage you added it manually, completely independent
from oVirt, during an unattended installation of the host
OS? In a production environment?<br>
<br>
Why?<br>
-----Ursprüngliche Nachricht-----<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Von:Nathanaël Blanchet <<a moz-do-not-send="true"
href="mailto:blanchet@abes.fr" target="_blank">blanchet@abes.fr</a>><br>
Gesendet: Fre 19 Juni 2015 14:09<br>
An: <a moz-do-not-send="true"
href="mailto:users@ovirt.org" target="_blank">users@ovirt.org</a><br>
Betreff: [ovirt-users] disaster recovery<br>
<br>
Hello all,<br>
<br>
Here is what can happen as a nightmare for a sysadmin:<br>
<br>
I installed a new host to my pool of pre existing ovirt
hosts with a<br>
kickstart file and a default partitionning. I used to do
this with vms<br>
that usually get one local disk.<br>
But..<br>
This time this host was attached to several existing ovirt
(production)<br>
lun and anaconda gathered all existing disk (local and
lun) into the<br>
same VG (lv_home) et formatted them with XFS....<br>
In the webadmin, the domain storage became unvailaible,
vms were still<br>
up (thankgoodness), but it was impossible to interact with
them. If I<br>
stopped them, it was impossible to reboot them. If I
launch lvs command,<br>
some hosts can still see the ovirt LV, but other see only
the lv_home<br>
while /dev/[idofvms] are still present.<br>
So it was my chance that vms were still present, and I
began to export<br>
them with a tar at file system level so as to import them
in a new<br>
domain storage.<br>
<br>
It seems that data are still present because the vms are
still running.<br>
So my question is really : instead of this difficult
export step, is<br>
there a way to recover the initial format of the ovirt lun
so as to make<br>
the lvm index come back on the disk?<br>
<br>
Any help or disaster experience would be much appreciated.<br>
<br>
-- <br>
Nathanaël Blanchet<br>
<br>
Supervision réseau<br>
Pôle Infrastrutures Informatiques<br>
227 avenue Professeur-Jean-Louis-Viala<br>
34193 MONTPELLIER CEDEX 5 <br>
Tél. 33 (0)4 67 54 84 55<br>
Fax 33 (0)4 67 54 84 14<br>
<a moz-do-not-send="true" href="mailto:blanchet@abes.fr"
target="_blank">blanchet@abes.fr</a><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true" href="mailto:Users@ovirt.org"
target="_blank">Users@ovirt.org</a><br>
<a moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users"
rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
<br>
</blockquote>
</blockquote>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true" href="mailto:Users@ovirt.org"
target="_blank">Users@ovirt.org</a><br>
<a moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users"
rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</blockquote>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Nathanaël Blanchet
Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
<a class="moz-txt-link-abbreviated" href="mailto:blanchet@abes.fr">blanchet@abes.fr</a> </pre>
</body>
</html>