6:25 p.m.
--=_0e272b5f-fcd6-4360-b961-925677073066
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
We had an incident where a VM hosts' disk filled up, the VMs all went unknown in the
web console, but were fully functional if you were to login or use the services of one. We
couldn't migrate them so we powered them down on that host and powered them up and let
ovirt choose the host for it, same as always. However the disk image on a few of them were
corrupted because once we fixed the host with the full disk, it still thought it should be
running the VM. Which promptly corrupted the disk, the error seems to be this in the logs:
2017-09-19 21:59:11,058 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
(DefaultQuartzScheduler3) [36c806f6] VM
'70cf75c7-0fc2-4bbe-958e-7d0095f70960'(testhub) is running in db and not running
on VDS 'ef6dc2a3-af6e-4e00-aa4
0-493b31263417'(vm-int7)
We upgraded to 4.1.6 from 4.0.6 earlier in the day, I don't really think it's
anything more than coincidence, but it's worrying enough to send to the community.
Regards,
Logan
--=_0e272b5f-fcd6-4360-b961-925677073066
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><body><div style=3D"font-family: Arial; font-size: 12pt; color:
#0000=
00"><div>We had an incident where a VM hosts' disk filled up, the VMs
all w=
ent unknown in the web console, but were fully functional if you were to lo=
gin or use the services of one. We couldn't migrate them so we powere=
d them down on that host and powered them up and let ovirt choose the host =
for it, same as always. However the disk image on a few of them were =
corrupted because once we fixed the host with the full disk, it still thoug=
ht it should be running the VM. Which promptly corrupted the disk, th=
e error seems to be this in the logs:</div><div><br
data-mce-bogus=3D"1"></=
div><div><span style=3D"font-family: monospace;"
data-mce-style=3D"font-fam=
ily: monospace;"><span style=3D"color: #000000; background-color:
#ffffff;"=
data-mce-style=3D"color: #000000; background-color: #ffffff;">2017-09-19 2=
1:59:11,058 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyz=
er] (DefaultQuartzScheduler3) [36c806f6] VM '70cf75c7-0fc2-4bbe-958e-7d0095=
f70960'(testhub) is </span><span style=3D"font-weight: bold; color:
#ff5454=
; background-color: #ffffff;" data-mce-style=3D"font-weight: bold; color: #=
ff5454; background-color: #ffffff;">running</span><span
style=3D"color: #00=
0000; background-color: #ffffff;" data-mce-style=3D"color: #000000; backgro=
und-color: #ffffff;"> in db and not </span><span
style=3D"font-weight: bold=
; color: #ff5454; background-color: #ffffff;" data-mce-style=3D"font-weight=
: bold; color: #ff5454; background-color: #ffffff;">running</span><span
sty=
le=3D"color: #000000; background-color: #ffffff;" data-mce-style=3D"color:
=
#000000; background-color: #ffffff;"> on VDS
'ef6dc2a3-af6e-4e00-aa4</span>=
<br>0-493b31263417'(vm-int7)<br></span></div><div><br></div><div>We
upgrade=
d to 4.1.6 from 4.0.6 earlier in the day, I don't really think it's anythin=
g more than coincidence, but it's worrying enough to send to the community.=
</div><div><br data-mce-bogus=3D"1"></div><div
data-marker=3D"__SIG_PRE__">=
Regards,<br>Logan</div></div></body></html>
--=_0e272b5f-fcd6-4360-b961-925677073066--
2621
days inactive
2621
days old
0 comments
1 participants
participants (1)
-
Logan Kuhn