[ovirt-users] vdsm issue

Daniel Helgenberger daniel.helgenberger at m-box.de
Fri Oct 24 08:23:21 UTC 2014


On 24.10.2014 09:02, John Michael Mercado wrote:
> Hi All,
Hi John,
>
> I need your help. Everytime the vdsm start, the server become *read-only  file 
> system*. My OS installed in SAN storage.
Reading your logs I can hardly believe this is a VDSM issue but rather
something more basic:
>
> I also got this error when i add the hosts "Host installation failed. Network 
> error during communication with the host."
>
> Here are some errors i got in /var/log/messages:
>
> Oct 24 14:24:27  init: libvirtd main process (3394) terminated with status 1
> Oct 24 14:24:27  init: libvirtd main process ended, respawning
> Oct 24 14:24:27  init: libvirtd main process (3410) terminated with status 1
> Oct 24 14:24:27  init: libvirtd main process ended, respawning
> Oct 24 14:24:27  init: libvirtd main process (3416) terminated with status 1
> Oct 24 14:24:27 init: libvirtd main process ended, respawning
> Oct 24 14:24:27 init: libvirtd main process (3420) terminated with status 1
> Oct 24 14:24:27 init: libvirtd main process ended, respawning
> Oct 24 14:24:27 init: libvirtd main process (3425) terminated with status 1
> Oct 24 14:24:27 init: libvirtd main process ended, respawning
> Oct 24 14:24:27 init: libvirtd main process (3434) terminated with status 1
> Oct 24 14:24:27 init: libvirtd main process ended, respawning
> Oct 24 14:24:27 init: libvirtd main process (3439) terminated with status 1
> Oct 24 14:24:27 init: libvirtd main process ended, respawning
> Oct 24 14:24:27 init: libvirtd main process (3443) terminated with status 1
> Oct 24 14:24:27 init: libvirtd main process ended, respawning
> Oct 24 14:24:27 init: libvirtd main process (3447) terminated with status 1
> Oct 24 14:24:27 init: libvirtd main process ended, respawning
> Oct 24 14:24:27 init: libvirtd main process (3457) terminated with status 1
> Oct 24 14:24:27 init: libvirtd main process ended, respawning
> Oct 24 14:24:27 init: libvirtd main process (3461) terminated with status 1
> Oct 24 14:24:27 init: libvirtd respawning too fast, stopped
> Oct 24 14:24:54 kernel: sd 1:0:0:0: rejecting I/O to offline device
> Oct 24 14:24:54 kernel: sd 1:0:2:0: rejecting I/O to offline device
> Oct 24 14:24:54 device-mapper: multipath: Failing path 8:64.
> Oct 24 14:24:54 multipathd: 8:64: mark as failed
> Oct 24 14:24:54 multipathd: 3600507680281077d680000000000001c: remaining active 
Can you detail why the path is failing?
> paths: 5
> Oct 24 14:24:54 kernel: sd 2:0:0:0: rejecting I/O to offline device
> Oct 24 14:24:54 kernel: sd 2:0:1:0: rejecting I/O to offline device
> Oct 24 14:24:54 kernel: sd 2:0:1:0: rejecting I/O to offline device
> Oct 24 14:24:54 kernel: device-mapper: multipath: Failing path 8:96.
> Oct 24 14:24:54 kernel: sd 2:0:2:0: rejecting I/O to offline device
> Oct 24 14:24:54 kernel: device-mapper: multipath: Failing path 8:112.
> Oct 24 14:24:54 kernel: sd 1:0:0:0: rejecting I/O to offline device
> Oct 24 14:24:54 kernel: device-mapper: multipath: Failing path 8:32.
> Oct 24 14:24:54 kernel: sd 1:0:1:0: rejecting I/O to offline device
> Oct 24 14:24:54 kernel: device-mapper: multipath: Failing path 8:48.
> Oct 24 14:24:54 kernel: sd 2:0:0:0: rejecting I/O to offline device
> Oct 24 14:24:54 kernel: device-mapper: multipath: Failing path 8:80.
> Oct 24 14:24:54 kernel: sd 2:0:2:0: rejecting I/O to offline device
> Oct 24 14:24:54 kernel: device-mapper: multipath: Failing path 8:112.
> Oct 24 14:24:54 kernel: sd 2:0:1:0: rejecting I/O to offline device
> Oct 24 14:24:54 kernel: device-mapper: multipath: Failing path 8:96.
> Oct 24 14:24:54 kernel: sd 1:0:2:0: rejecting I/O to offline device
> Oct 24 14:24:54 kernel: device-mapper: multipath: Failing path 8:64.
> Oct 24 14:24:54 kernel: Buffer I/O error on device dm-2, logical block 132850
> Oct 24 14:24:54 kernel: lost page write due to I/O error on dm-2
> Oct 24 14:24:54 kernel: Buffer I/O error on device dm-2, logical block 577540
> Oct 24 14:24:54 kernel: lost page write due to I/O error on dm-2
Is dm-2 the failed path by any chance? Otherwise dm-2 seems quite a low
number, this can be your root LV? However, I would investigate your
multipath setup.
Also, try to write some files (dd if=/dev/zero
of=/path/to/shared/storage bs=4m).
>
> Hope you can help me.
>
> Thanks

-- 
Daniel Helgenberger
m box bewegtbild GmbH

P: +49/30/2408781-22
F: +49/30/2408781-10

ACKERSTR. 19
D-10115 BERLIN


www.m-box.de  www.monkeymen.tv

Geschäftsführer: Martin Retschitzegger / Michaela Göllner
Handeslregister: Amtsgericht Charlottenburg / HRB 112767




More information about the Users mailing list