[ovirt-users] Re: VDO + HCI = failed reboots

On Mon, Aug 27, 2018 at 5:49 PM, Donny Davis <donny(a)fortnebula.com&gt; wrote: > I just spun up the latest and greatest ovirt has to offer, and I am > building out an HCI cluster. The deployment went wonderfully. I had dns > setup for everything, and it just worked. Great job team! > > I just wanted to add in something i noticed after rebooting the nodes. > The gluster service, and volumes would not come back up after rebooting. I > found that there needs to be an entry in the fstab for the gluster logical > volumes to tell them to start the vdo service. So without this, the node > will fail to boot if you are using vdo. > > inode64,noatime,nodiratime,discard,x-systemd.requires=vdo.service > > the defaults are this > inode64,noatime,nodiratime > This was fixed in gdeploy - https://bugzilla.redhat.com/ show_bug.cgi?id=1548399 Can you tell us the version of gdeploy you used? # rpm -qa | grep gdeploy > > Hopefully it helps someone else > > :) > Cheers > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/communit > y/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archiv > es/list/users(a)ovirt.org/message/K7MXXDAVPR23IR7ASXT5P73AA3W3AWVW/ > >