<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><font size="-1">Hi everyone,<br>
<br>
<font size="-1">Thank you for your responses.<br>
<br>
<font size="-1">Yeela:</font></font></font><br>
<small><i>>When oVirt started the vm it mounted the corrupt
disk image that seemed fine, but it couldn't find the OS
because of the corrupted fs,
and the error caused it to pause the guest.</i><br>
<br>
To clear things up it was the /var mount that had the corrupted
filesystem, not the guest's root filesystem.<br>
oVirt still continued to pause the guest even when I had booted
the guest off a CentOS DVD ISO, run rescue mode and manually
activated the /var logical volume. In this case I did not
activate or mount the guests root filesystem and only activated
the guests /var filesystem so that I could fsck it. fsck would
run for around 5-10 minutes with the message "Deleting orphaned
inode......" and then oVirt would simply pause the entire guest.<br>
The only information I could find was on the physical host's
vdsm.log, which specified the following:<br>
</small><font size="-1"><font size="-1"><font size="-1"><font
size="-1"><font size="-1"><font size="-1"><font size="-1"><font
size="-1"><font size="-1"><font size="-1"><font
size="-1"><font size="-1"><font size="-1"><font
size="-1"><font size="-1"><font
size="-1"><font size="-1"><i>libvirtEventLoop::<a
class="moz-txt-link-freetext" href="INFO::2012-12-02">INFO::2012-12-02</a>
09:05:50,296::libvirtvm::1965::vm.Vm::(_onAbnormalStop)
vmId=`23b9212c-1e25-4003-aa18-b1e819bf6bb1`::abnormal
vm stop device ide0-0-1 error
eother<br>
<br>
</i><font size="-1"><font
size="-1">Perh<font
size="-1">aps there was
another log I should have
examined to see if more i<font
size="-1">nforma<font
size="-1">tion was
provided about wh<font
size="-1">y oVirt
was pausing the
guest?<br>
<br>
</font></font></font></font></font></font><i></i><font
size="-1"><font size="-1"><br>
<br>
Shu:<br>
<font size="-1">This is what
I did to dd the images
off, and to <font
size="-1">work around
the problem<font
size="-1">:<br>
</font></font><font
size="-1">1.) <font
size="-1">O<font
size="-1">n the
physical host<font
size="-1">:</font>
<font size="-1">C</font></font>reated
an NFS mount to
another temporary
Linux system that had
sufficient storage for
the 500GB filesystem<br>
<font size="-1">2.<font
size="-1">) O<font
size="-1">n</font>
the physical host<font
size="-1">: <font
size="-1">U</font></font>sed
'dd' to <font
size="-1">dump
the /var
filesystem's
logical vol<font
size="-1">ume
to an image
file<font
size="-1"> <font
size="-1">via
NFS on t<font
size="-1">he
temporar<font
size="-1">y</font>
Linux <font
size="-1">system</font></font></font>.</font></font></font></font></font><br>
<font size="-1">3.) On
the temporary Linux
s<font size="-1">ystem
that now contained
the filesystem
image file, I ran
"qemu-img info</font></font>"
and noticed that the<font
size="-1"> fi<font
size="-1">lesystem</font>
image was <font
size="-1">qc<font
size="-1">ow2 <font
size="-1">type</font>
and</font></font>
specified a ba<font
size="-1">cking
file.<br>
<font size="-1">4.)
On t<font
size="-1">he
physical host<font
size="-1">:
Used <font
size="-1">'dd'
to dump <font
size="-1">the
lo<font
size="-1">gical
volume
specified as a
backing file,
to an image
file </font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font><font
size="-1"><font size="-1"><font size="-1"><font size="-1"><font
size="-1"><font size="-1"><font size="-1"><font
size="-1"><font size="-1"><font size="-1"><font
size="-1"><font size="-1"><font size="-1"><font
size="-1"><font size="-1"><font
size="-1"><font size="-1"><font
size="-1"><font size="-1"><font
size="-1"><font size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1"><font
size="-1">via
NFS on t<font
size="-1">he
temporar<font
size="-1">y</font>
Linux <font
size="-1">system.<br>
<font
size="-1">5.<font
size="-1">) On
the <font
size="-1">temporary
Linux system:
Used '<font
size="-1">qemu-img
reba<font
size="-1">se</font>'
to change the
backing file <font
size="-1">to
the local copy<font
size="-1"> of
the back<font
size="-1">ing
file image.</font></font></font></font></font></font></font><br>
<font
size="-1">6.)
On the
temporary
Linux system:
Used 'qemu-img
commit' to
commit the
changes stored
in the
filesystem
image file to
the backing
file image.<br>
<font
size="-1">7.)
O<font
size="-1">n
the temporary
Linux sy<font
size="-1">ste<font
size="-1">m<font
size="-1">: U<font
size="-1">sed
'qemu-img
convert' to
convert the
backing file
image to raw
format.<br>
<font
size="-1">8.)
On<font
size="-1"> <font
size="-1">the
<font
size="-1">temporary
Linux system:
<font
size="-1">Used
'losetup', <font
size="-1">'kpart'<font
size="-1"><font
size="-1"> and
</font>'fsck'</font></font></font></font></font></font></font>
to <font
size="-1">repair
the backing
file image.
Fsck displayed
t<font
size="-1">he
same 'Del<font
size="-1">eting
<font
size="-1">orphaned
in<font
size="-1">ode<font
size="-1">....'
<font
size="-1">message</font></font></font></font></font></font></font>
<font
size="-1">but
managed to <font
size="-1">con<font
size="-1">tinue
and completed
ok.<br>
<font
size="-1">9.)
O<font
size="-1">n
the tempo<font
size="-1">rary
Linux system:
<font
size="-1">Mo<font
size="-1">unted
the loop
filesystem and
confirmed that
<font
size="-1">the
<font
size="-1">data
was intact and
was current.</font></font></font></font></font></font></font><br>
</font></font></font><font
size="-1"><font
size="-1">10</font>.)
I<font
size="-1">n <font
size="-1">the
oVirt GUI:
Deactivated
the faulty
Virtual <font
size="-1">D</font>isk
attached to
the guest.</font></font></font><br>
<font
size="-1"><font
size="-1">11</font>.)
In the oVirt
GUI: Created a
new
'preallocated<font
size="-1">' <font
size="-1">Virtual
Disk <font
size="-1">of
sufficient
size<font
size="-1"> for
the guest.<br>
<font
size="-1">1<font
size="-1">2</font>.)
O<font
size="-1">n
the physical
host: Used <font
size="-1">'dd'
to upload the
<font
size="-1">raw
ba<font
size="-1">cking
file image
from (7) to
the new lo<font
size="-1">gical
volume.</font></font></font></font></font></font><br>
<font
size="-1">1<font
size="-1">3</font>.)
<font
size="-1">I
then conf<font
size="-1">igured
the guest to
boot from the
CentOS <font
size="-1">D<font
size="-1">VD
ISO into res<font
size="-1">cue
mode<font
size="-1"> to
confirm that
the <font
size="-1">lo<font
size="-1">gical
<font
size="-1">volume
<font
size="-1"><font
size="-1">for
th<font
size="-1">e <font
size="-1"><font
size="-1">guest<font
size="-1">'s
/var </font></font>filesystem</font></font>
was accessi<font
size="-1">ble
and mountable.<br>
<font
size="-1">1<font
size="-1">4</font>.)
<font
size="-1">Reconfigured
the guest to
boo<font
size="-1">t<font
size="-1">
from it's <font
size="-1">primary
<font
size="-1">Virtual
Disk</font></font>
and sta<font
size="-1">rted
up the guest.</font></font></font></font></font><br>
</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font><br>
</font><br>
</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font><i></i></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font><br>
<br>
<br>
<br>
<br>
<div class="moz-signature">
<br>
<br>
Get important Linux and industry-related news at: <a
href="http://facebook.com/dcdata">facebook.com/dcdata</a><br>
<br>
<font color="#000000"><font face="arial" size="2">Kind regards,</font><br>
<br>
<font color="#000000"><font face="arial"><font size="4">David
Wilson</font></font></font><br>
<font color="#000000"><font face="arial"><font size="1">CNS,CLS,
LINUX+, CLA, DCTS, LPIC3</font></font></font><br>
<font color="#0779b5"><font face="arial"><font size="3"><b>LinuxTech
CC t/a DcData</b></font></font></font><br>
<font color="#0779b5"><font face="arial"><font size="1">CK
number: 2001/058368/23</font></font></font><br>
<table border="0">
<tbody>
<tr>
<td width="75"><font color="#000000"><font face="arial"><font
size="2"><b>Website:</b></font></font></font></td>
<td><font color="#000000"><font face="arial"><font
size="2"><a class="moz-txt-link-freetext" href="http://www.dcdata.co.za">http://www.dcdata.co.za</a></font></font></font></td>
</tr>
<tr>
<td><font color="#000000"><font face="arial"><font
size="2"><b>Support:</b></font></font></font></td>
<td><font color="#000000"><font face="arial"><font
size="2">+27(0)860-1-LINUX</font></font></font></td>
</tr>
<tr>
<td><font color="#000000"><font face="arial"><font
size="2"><b>Mobile:</b></font></font></font></td>
<td><font color="#000000"><font face="arial"><font
size="2">+27(0)824147413</font></font></font></td>
</tr>
<tr>
<td><font color="#000000"><font face="arial"><font
size="2"><b>Tel:</b></font></font></font></td>
<td><font color="#000000"><font face="arial"><font
size="2">+27(0)333446100</font></font></font></td>
</tr>
<tr>
<td><font color="#000000"><font face="arial"><font
size="2"><b>Fax:</b></font></font></font></td>
<td><font color="#000000"><font face="arial"><font
size="2">+27(0)866878971</font></font></font></td>
</tr>
</tbody>
</table>
</font></div>
On 12/03/2012 01:07 PM, Dan Kenigsberg wrote:<br>
</div>
<blockquote cite="mid:20121203110737.GD20719@redhat.com" type="cite">
<pre wrap="">On Mon, Dec 03, 2012 at 04:37:01AM -0500, Yeela Kaplan wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Glad to hear it worked out.
When oVirt started the vm it mounted the corrupt disk image that seemed fine,
but it couldn't find the OS because of the corrupted fs,
and the error caused it to pause the guest.
</pre>
</blockquote>
<pre wrap="">
I think we should be a bit more exact here: a VM without an installed OS
does not pause. The cause of the pause was, most probably, and attempt
to read from a corrupted qcow. When qemu fails to serve the guest with
data due to a bug in the underlying storage, qemu stops and waits for
further instructions from management. We use this feature for automatic
lv-extend (on enospace error). But here, with eother error, a human
intervension is required.
</pre>
</blockquote>
<br>
<br><br>
<p style="font-family: Verdana; font-size:8pt; color:#666666;" align="justify">
Time to evaluate your email security provider? <a href="http://www.mimecast.com/emailsecurity/">Watch the video</a> and take advantage of Mimecast’s first ever limited promotion.
</p>
</body>
</html>