Hi Michael,

I know how you feel abiut VDO. I wass in the same boat until I starrted using 
systemd's mount units.Since then I do not have any issues.

For now try the following:
Boot 1 host via rescue dvd , chroot into the system and install the vdo and 
kvdo  packages (maybe reinstall is more correct) .
Once then, try to run the vdo service (still in chroot) and try to make it work.
Then, just rebuild the initramfs (dracut -f -k kernel-version) and reboot.
Check if your VDO, bricks  and Gluster are operational again.

If yes, do the other nodes.
Once done - run 'gluster volume  heal my-volume full' (replace my-volume with 
actual name).
This will force gluster to sync all bricks.

P.S.: Now, I'm using gluster snapshot for recovery between engine upgrades 
(HostedEngine is stopped while makking the snapahot).

Best Regards,
Strahil NikolovOn Apr 21, 2019 20:44, mich...@wanderingmad.com wrote:
>
> I updated my ovirt from 4.3.2 to 4.3.3 and everything went bad, my gluster 
> volumes were constantly dropping out and getting unsynced and everything was 
> just running slower than molasses.  So I thought I would reload the hosts 
> from ovirt node to Centos and re-do the storage, thinking that may help.  I 
> tried using centos, but I was never able to add centos hosts back to the 
> ovirt engine due to a gluster error in the logs, so I went and downloaded 
> ovirt node 4.3.3, and now after spending an hour reloading all the servers 
> with ovirt node, One of the nodes I can't access the cockpit on, and the 
> other two have broken VDO modules, the modules are installed but don't exist 
> in the kernel, and when I removed the module, I lost all network 
> configuration, and when I re-installed it, I get a scriptlet error on 
> compilation and there is still a missing VDO module.  This is now the 3rd 
> time i've hit this VDO issue and i'm really frustrated right now, should I 
> just go back to 4.3.2?  I just redownloa 
> ded the latest 4.3.3 ISO today.
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/QA2SMYRZCXQYRT2BNYW2RSFPKZS7VQBC/
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/65XFYTS6WVCPT5JDPH6XKWMNGJF4RHI5/

Reply via email to