[ovirt-users] Re: oVirt 4.4.0 Beta release refresh is now available for testing
On Fri, Apr 17, 2020 at 6:40 PM Sandro Bonazzola wrote: > oVirt 4.4.0 Beta release refresh is now available for testing > > The oVirt Project is excited to announce the availability of the beta > release of oVirt 4.4.0 refresh (beta 4) for testing, as of April 17th, 2020 > > This release unleashes an altogether more powerful and flexible open > source virtualization solution that encompasses hundreds of individual > changes and a wide range of enhancements across the engine, storage, > network, user interface, and analytics on top of oVirt 4.3. > > > Hello, I have tried the iso of ovirt node ng to configure a single host HCI environment. Using the wizard for single node, at the beginning in the window where you have to insert the fqdn of the storage node I see a javascript exception (a red Ooops! in top right of cockpit page tells me that). Both on Google Chrome and in firefox. In practice you cannot type anything and in js console of chrome I see: app.js:43 Uncaught TypeError: Cannot read property 'checked' of null at n.value (app.js:43) at changeCallBack (app.js:43) at Object.b (app.js:27) at w (app.js:27) at app.js:27 at S (app.js:27) at T (app.js:27) at Array.forEach () at _ (app.js:27) at N (app.js:27) Sort of workaround is to type a character (you don't see anything), then click the ipv6 related checkbox just above the input line, and then you see the first character, then again, alternating the checkbox and a character you see every time appear the new character typed. You cannot type the full fqdn in one flow because only the last character appears then when you click on the checkbox... This anyway let me continue and type the whole storage hostname and go ahead with the installation. I arrive up to the final step "Finish Deployment", but when the host exits final global maintenance and the engine VM starts, it goes into panic and I realized that I missed the pass-through cpu flag for the hypervisor vm, so I'm going to retry. In the mean time can anyone verify the javascript exception above? Gianluca ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IKBLU764LCRHHEXCXL4MYGPIUXJEANXX/
[ovirt-users] Re: oVirt 4.3.7 + Gluster 6.6 unsynced entries
On April 18, 2020 5:58:03 PM GMT+03:00, Adrian Quintero wrote: >ok I did that however I still dont see ".gfid", thoughts? > >[root@host1]# mount -t glusterfs -o aux-gfid-mount >192.168.0.59:/vmstore >/mnt/vmstore > > >[root@host1]# getfattr -n trusted.glusterfs.pathinfo -e text >/mnt/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6/ >getfattr: Removing leading '/' from absolute path names > ># file: mnt/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6/ >trusted.glusterfs.pathinfo="( > > >)" > > >Thanks, > > > > > >On Sat, Apr 18, 2020 at 10:44 AM Adrian Quintero > >wrote: > >> ah ok.. >> want me to do it on any of the hosts? >> >> On Sat, Apr 18, 2020 at 10:34 AM Strahil Nikolov > >> wrote: >> >>> On April 18, 2020 4:46:35 PM GMT+03:00, Adrian Quintero < >>> adrianquint...@gmail.com> wrote: >>> >Hi Strahil, >>> >Here are my findings >>> > >>> > >>> >1.- mount -t glusterfs -o aux-gfid-mount host1:vmstore /mnt/vmstore >>> > >>> >[root@host3]# mount -t glusterfs -o aux-gfid-mount >>> >192.168.0.59:/vmstore >>> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >>> >/sbin/mount.glusterfs: according to mtab, GlusterFS is already >mounted >>> >on >>> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >>> > >>> >[root@host2]# mount -t glusterfs -o aux-gfid-mount >>> >192.168.0.59:/vmstore >>> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >>> >/sbin/mount.glusterfs: according to mtab, GlusterFS is already >mounted >>> >on >>> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >>> > >>> >[root@host1]# mount -t glusterfs -o aux-gfid-mount >>> >192.168.0.59:/vmstore >>> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >>> >/sbin/mount.glusterfs: according to mtab, GlusterFS is already >mounted >>> >on >>> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >>> > >>> > >>> >2.-getfattr -n trusted.glusterfs.pathinfo -e text >>> >/mnt/vmstore/.gfid/5aeb168c-b8e3-4581-97f9-eafc33f2f318 >>> >I am not to sure about this one as I cant find ".gfid" anywhere. >>> > >>> >3.-umount /mnt/vmstore >>> > I did not try this one yet. >>> > >>> >Question? the umount was tobe tested on host3 ? >>> > >>> >glusterfs 6.6 >>> > >>> >Thanks you, >>> > >>> >Adrian >>> > >>> > >>> > >>> >On Sat, Apr 18, 2020 at 3:53 AM Strahil Nikolov > >>> >wrote: >>> > >>> >> On April 16, 2020 9:27:11 PM GMT+03:00, adrianquint...@gmail.com >>> >wrote: >>> >> >Hi Strahil, >>> >> >This is what method 2 came up with: >>> >> > >>> >> >[root@host1 ~]# getfattr -n trusted.glusterfs.pathinfo -e text >>> >> >/rhev/data-center/mnt/glusterSD/192.168.0.59\:_vmstore/ >>> >> >getfattr: Removing leading '/' from absolute path names >>> >> ># file: rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore/ >>> >> >trusted.glusterfs.pathinfo="( >>> >> >>> >> >>> >>> >>> >>> >> >>> >> >>> >>> >>> >>> >> >>> >> >>> >>> >>>)" >>> >> > >>> >> > >>> >> >I will try method 1, but just want to make sure I am running it >>> >against >>> >> >the correct file directory. >>> >> >___ >>> >> >Users mailing list -- users@ovirt.org >>> >> >To unsubscribe send an email to users-le...@ovirt.org >>> >> >Privacy Statement: https://www.ovirt.org/privacy-policy.html >>> >> >oVirt Code of Conduct: >>> >> >https://www.ovirt.org/community/about/community-guidelines/ >>> >> >List Archives: >>> >> > >>> >> >>> > >>> >https://lists.ovirt.org/archives/list/users@ovirt.org/message/7377A4JQ54AYWBIVGJ6XJLG5THCGETH3/ >>> >> >>> >> Hey Adrian, >>> >> >>> >> Can you provide the output of the following: >>> >> >>> >> mount -t glusterfs -o aux-gfid-mount host1:vmstore /mnt/vmstore >>> >> >>> >> >>> >> getfattr -n trusted.glusterfs.pathinfo -e text >>> >> /mnt/vmstore/.gfid/5aeb168c-b8e3-4581-97f9-eafc33f2f318 >>> >> >>> >> umount /mnt/vmstore >>> >> >>> >> Best Regards, >>> >> Strahil Nikolov >>> >> >>> >> >>> >>> You can't remount gluster ... >>> Juat mount it on /mnt just like my example. Once you mount it with >that >>> option , the '.gfid' will be exposed to you. >>> >>> Best Regards, >>> Strahil Nikolov >>> >> >> >> -- >> Adrian Quintero >> '.gfid' is a virtual folder. You can try to 'stat' the folder from the previous output and give it some time (15 - 20 min) to selfheal. Best Regards, Strahil Nikolov ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/6X5SYBPLBLXRMSUETL7SW6LIYQOKMIMK/
[ovirt-users] Re: Enabling VT-d causes hard lockup
i had similar things with faulty 10G network card, so u have any devices in pci slots? brw the card should have as well sr-iov on. Strahil Nikolov schrieb am Fr., 17. Apr. 2020, 18:54: > On April 17, 2020 6:04:02 PM GMT+03:00, Shareef Jalloq < > shar...@jalloq.co.uk> wrote: > >Hi, > > > >I've been trying to get an old machine setup for PCIe passthrough but > >am > >seeing kernel hangs when booting into oVirt. This is a Supermicro > >X10DAi > >with dual E5-2695 V4's I think. > > > >I had VT-d enabled and added SR-IOV. Don't think there's anything > >else I > >need to enable in the BIOS is there? I just updated to the latest > >version > >for this board too. > > > >It always seems to be CPU#18 too : > >https://photos.app.goo.gl/HG7NcyWwfuq646HeA > > > >Shareef. > > There should be an IOMMU option too. > > The following is for AMD, but maybe it's valid for intel: > > https://www.supermicro.com/support/faqs/faq.cfm?faq=21348 > > Best Regards, > Strahil Nikolov > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/DNENAMYE77D3GRBU5IXF54IORYWPHBS3/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AY3HEI3M3C4O6YTNA4QMDPYEBQRVJVG7/
[ovirt-users] Re: oVirt 4.3.7 + Gluster 6.6 unsynced entries
ok I did that however I still dont see ".gfid", thoughts? [root@host1]# mount -t glusterfs -o aux-gfid-mount 192.168.0.59:/vmstore /mnt/vmstore [root@host1]# getfattr -n trusted.glusterfs.pathinfo -e text /mnt/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6/ getfattr: Removing leading '/' from absolute path names # file: mnt/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6/ trusted.glusterfs.pathinfo="( )" Thanks, On Sat, Apr 18, 2020 at 10:44 AM Adrian Quintero wrote: > ah ok.. > want me to do it on any of the hosts? > > On Sat, Apr 18, 2020 at 10:34 AM Strahil Nikolov > wrote: > >> On April 18, 2020 4:46:35 PM GMT+03:00, Adrian Quintero < >> adrianquint...@gmail.com> wrote: >> >Hi Strahil, >> >Here are my findings >> > >> > >> >1.- mount -t glusterfs -o aux-gfid-mount host1:vmstore /mnt/vmstore >> > >> >[root@host3]# mount -t glusterfs -o aux-gfid-mount >> >192.168.0.59:/vmstore >> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >> >/sbin/mount.glusterfs: according to mtab, GlusterFS is already mounted >> >on >> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >> > >> >[root@host2]# mount -t glusterfs -o aux-gfid-mount >> >192.168.0.59:/vmstore >> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >> >/sbin/mount.glusterfs: according to mtab, GlusterFS is already mounted >> >on >> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >> > >> >[root@host1]# mount -t glusterfs -o aux-gfid-mount >> >192.168.0.59:/vmstore >> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >> >/sbin/mount.glusterfs: according to mtab, GlusterFS is already mounted >> >on >> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >> > >> > >> >2.-getfattr -n trusted.glusterfs.pathinfo -e text >> >/mnt/vmstore/.gfid/5aeb168c-b8e3-4581-97f9-eafc33f2f318 >> >I am not to sure about this one as I cant find ".gfid" anywhere. >> > >> >3.-umount /mnt/vmstore >> > I did not try this one yet. >> > >> >Question? the umount was tobe tested on host3 ? >> > >> >glusterfs 6.6 >> > >> >Thanks you, >> > >> >Adrian >> > >> > >> > >> >On Sat, Apr 18, 2020 at 3:53 AM Strahil Nikolov >> >wrote: >> > >> >> On April 16, 2020 9:27:11 PM GMT+03:00, adrianquint...@gmail.com >> >wrote: >> >> >Hi Strahil, >> >> >This is what method 2 came up with: >> >> > >> >> >[root@host1 ~]# getfattr -n trusted.glusterfs.pathinfo -e text >> >> >/rhev/data-center/mnt/glusterSD/192.168.0.59\:_vmstore/ >> >> >getfattr: Removing leading '/' from absolute path names >> >> ># file: rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore/ >> >> >trusted.glusterfs.pathinfo="( >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >>)" >> >> > >> >> > >> >> >I will try method 1, but just want to make sure I am running it >> >against >> >> >the correct file directory. >> >> >___ >> >> >Users mailing list -- users@ovirt.org >> >> >To unsubscribe send an email to users-le...@ovirt.org >> >> >Privacy Statement: https://www.ovirt.org/privacy-policy.html >> >> >oVirt Code of Conduct: >> >> >https://www.ovirt.org/community/about/community-guidelines/ >> >> >List Archives: >> >> > >> >> >> > >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/7377A4JQ54AYWBIVGJ6XJLG5THCGETH3/ >> >> >> >> Hey Adrian, >> >> >> >> Can you provide the output of the following: >> >> >> >> mount -t glusterfs -o aux-gfid-mount host1:vmstore /mnt/vmstore >> >> >> >> >> >> getfattr -n trusted.glusterfs.pathinfo -e text >> >> /mnt/vmstore/.gfid/5aeb168c-b8e3-4581-97f9-eafc33f2f318 >> >> >> >> umount /mnt/vmstore >> >> >> >> Best Regards, >> >> Strahil Nikolov >> >> >> >> >> >> You can't remount gluster ... >> Juat mount it on /mnt just like my example. Once you mount it with that >> option , the '.gfid' will be exposed to you. >> >> Best Regards, >> Strahil Nikolov >> > > > -- > Adrian Quintero > -- Adrian Quintero ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/C3AYJ3P7P7SU3UP6Z5E65KZIPBXVRN6R/
[ovirt-users] Re: oVirt 4.3.7 + Gluster 6.6 unsynced entries
ah ok.. want me to do it on any of the hosts? On Sat, Apr 18, 2020 at 10:34 AM Strahil Nikolov wrote: > On April 18, 2020 4:46:35 PM GMT+03:00, Adrian Quintero < > adrianquint...@gmail.com> wrote: > >Hi Strahil, > >Here are my findings > > > > > >1.- mount -t glusterfs -o aux-gfid-mount host1:vmstore /mnt/vmstore > > > >[root@host3]# mount -t glusterfs -o aux-gfid-mount > >192.168.0.59:/vmstore > >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > >/sbin/mount.glusterfs: according to mtab, GlusterFS is already mounted > >on > >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > > > >[root@host2]# mount -t glusterfs -o aux-gfid-mount > >192.168.0.59:/vmstore > >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > >/sbin/mount.glusterfs: according to mtab, GlusterFS is already mounted > >on > >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > > > >[root@host1]# mount -t glusterfs -o aux-gfid-mount > >192.168.0.59:/vmstore > >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > >/sbin/mount.glusterfs: according to mtab, GlusterFS is already mounted > >on > >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > > > > > >2.-getfattr -n trusted.glusterfs.pathinfo -e text > >/mnt/vmstore/.gfid/5aeb168c-b8e3-4581-97f9-eafc33f2f318 > >I am not to sure about this one as I cant find ".gfid" anywhere. > > > >3.-umount /mnt/vmstore > > I did not try this one yet. > > > >Question? the umount was tobe tested on host3 ? > > > >glusterfs 6.6 > > > >Thanks you, > > > >Adrian > > > > > > > >On Sat, Apr 18, 2020 at 3:53 AM Strahil Nikolov > >wrote: > > > >> On April 16, 2020 9:27:11 PM GMT+03:00, adrianquint...@gmail.com > >wrote: > >> >Hi Strahil, > >> >This is what method 2 came up with: > >> > > >> >[root@host1 ~]# getfattr -n trusted.glusterfs.pathinfo -e text > >> >/rhev/data-center/mnt/glusterSD/192.168.0.59\:_vmstore/ > >> >getfattr: Removing leading '/' from absolute path names > >> ># file: rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore/ > >> >trusted.glusterfs.pathinfo="( > >> > >> > > >> > >> > >> > > >> > >> > >> > > >>)" > >> > > >> > > >> >I will try method 1, but just want to make sure I am running it > >against > >> >the correct file directory. > >> >___ > >> >Users mailing list -- users@ovirt.org > >> >To unsubscribe send an email to users-le...@ovirt.org > >> >Privacy Statement: https://www.ovirt.org/privacy-policy.html > >> >oVirt Code of Conduct: > >> >https://www.ovirt.org/community/about/community-guidelines/ > >> >List Archives: > >> > > >> > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/7377A4JQ54AYWBIVGJ6XJLG5THCGETH3/ > >> > >> Hey Adrian, > >> > >> Can you provide the output of the following: > >> > >> mount -t glusterfs -o aux-gfid-mount host1:vmstore /mnt/vmstore > >> > >> > >> getfattr -n trusted.glusterfs.pathinfo -e text > >> /mnt/vmstore/.gfid/5aeb168c-b8e3-4581-97f9-eafc33f2f318 > >> > >> umount /mnt/vmstore > >> > >> Best Regards, > >> Strahil Nikolov > >> > >> > > You can't remount gluster ... > Juat mount it on /mnt just like my example. Once you mount it with that > option , the '.gfid' will be exposed to you. > > Best Regards, > Strahil Nikolov > -- Adrian Quintero ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/CQXPXPOSZ5FQAQPY4WQP7LYITFXVKXZQ/
[ovirt-users] Re: oVirt 4.3.7 + Gluster 6.6 unsynced entries
On April 18, 2020 4:46:35 PM GMT+03:00, Adrian Quintero wrote: >Hi Strahil, >Here are my findings > > >1.- mount -t glusterfs -o aux-gfid-mount host1:vmstore /mnt/vmstore > >[root@host3]# mount -t glusterfs -o aux-gfid-mount >192.168.0.59:/vmstore >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >/sbin/mount.glusterfs: according to mtab, GlusterFS is already mounted >on >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > >[root@host2]# mount -t glusterfs -o aux-gfid-mount >192.168.0.59:/vmstore >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >/sbin/mount.glusterfs: according to mtab, GlusterFS is already mounted >on >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > >[root@host1]# mount -t glusterfs -o aux-gfid-mount >192.168.0.59:/vmstore >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore >/sbin/mount.glusterfs: according to mtab, GlusterFS is already mounted >on >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > > >2.-getfattr -n trusted.glusterfs.pathinfo -e text >/mnt/vmstore/.gfid/5aeb168c-b8e3-4581-97f9-eafc33f2f318 >I am not to sure about this one as I cant find ".gfid" anywhere. > >3.-umount /mnt/vmstore > I did not try this one yet. > >Question? the umount was tobe tested on host3 ? > >glusterfs 6.6 > >Thanks you, > >Adrian > > > >On Sat, Apr 18, 2020 at 3:53 AM Strahil Nikolov >wrote: > >> On April 16, 2020 9:27:11 PM GMT+03:00, adrianquint...@gmail.com >wrote: >> >Hi Strahil, >> >This is what method 2 came up with: >> > >> >[root@host1 ~]# getfattr -n trusted.glusterfs.pathinfo -e text >> >/rhev/data-center/mnt/glusterSD/192.168.0.59\:_vmstore/ >> >getfattr: Removing leading '/' from absolute path names >> ># file: rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore/ >> >trusted.glusterfs.pathinfo="( >> >> >> >> >> >> >> >> >>)" >> > >> > >> >I will try method 1, but just want to make sure I am running it >against >> >the correct file directory. >> >___ >> >Users mailing list -- users@ovirt.org >> >To unsubscribe send an email to users-le...@ovirt.org >> >Privacy Statement: https://www.ovirt.org/privacy-policy.html >> >oVirt Code of Conduct: >> >https://www.ovirt.org/community/about/community-guidelines/ >> >List Archives: >> > >> >https://lists.ovirt.org/archives/list/users@ovirt.org/message/7377A4JQ54AYWBIVGJ6XJLG5THCGETH3/ >> >> Hey Adrian, >> >> Can you provide the output of the following: >> >> mount -t glusterfs -o aux-gfid-mount host1:vmstore /mnt/vmstore >> >> >> getfattr -n trusted.glusterfs.pathinfo -e text >> /mnt/vmstore/.gfid/5aeb168c-b8e3-4581-97f9-eafc33f2f318 >> >> umount /mnt/vmstore >> >> Best Regards, >> Strahil Nikolov >> >> You can't remount gluster ... Juat mount it on /mnt just like my example. Once you mount it with that option , the '.gfid' will be exposed to you. Best Regards, Strahil Nikolov ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/EXYIGWTA7BCD3GIQRUEZNPZIU7TW2QKD/
[ovirt-users] Re: oVirt 4.3.7 + Gluster 6.6 unsynced entries
Hi Strahil, Here are my findings 1.- mount -t glusterfs -o aux-gfid-mount host1:vmstore /mnt/vmstore [root@host3]# mount -t glusterfs -o aux-gfid-mount 192.168.0.59:/vmstore /rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore /sbin/mount.glusterfs: according to mtab, GlusterFS is already mounted on /rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore [root@host2]# mount -t glusterfs -o aux-gfid-mount 192.168.0.59:/vmstore /rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore /sbin/mount.glusterfs: according to mtab, GlusterFS is already mounted on /rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore [root@host1]# mount -t glusterfs -o aux-gfid-mount 192.168.0.59:/vmstore /rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore /sbin/mount.glusterfs: according to mtab, GlusterFS is already mounted on /rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore 2.-getfattr -n trusted.glusterfs.pathinfo -e text /mnt/vmstore/.gfid/5aeb168c-b8e3-4581-97f9-eafc33f2f318 I am not to sure about this one as I cant find ".gfid" anywhere. 3.-umount /mnt/vmstore I did not try this one yet. Question? the umount was tobe tested on host3 ? glusterfs 6.6 Thanks you, Adrian On Sat, Apr 18, 2020 at 3:53 AM Strahil Nikolov wrote: > On April 16, 2020 9:27:11 PM GMT+03:00, adrianquint...@gmail.com wrote: > >Hi Strahil, > >This is what method 2 came up with: > > > >[root@host1 ~]# getfattr -n trusted.glusterfs.pathinfo -e text > >/rhev/data-center/mnt/glusterSD/192.168.0.59\:_vmstore/ > >getfattr: Removing leading '/' from absolute path names > ># file: rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore/ > >trusted.glusterfs.pathinfo="( > > > > > > > > >)" > > > > > >I will try method 1, but just want to make sure I am running it against > >the correct file directory. > >___ > >Users mailing list -- users@ovirt.org > >To unsubscribe send an email to users-le...@ovirt.org > >Privacy Statement: https://www.ovirt.org/privacy-policy.html > >oVirt Code of Conduct: > >https://www.ovirt.org/community/about/community-guidelines/ > >List Archives: > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/7377A4JQ54AYWBIVGJ6XJLG5THCGETH3/ > > Hey Adrian, > > Can you provide the output of the following: > > mount -t glusterfs -o aux-gfid-mount host1:vmstore /mnt/vmstore > > > getfattr -n trusted.glusterfs.pathinfo -e text > /mnt/vmstore/.gfid/5aeb168c-b8e3-4581-97f9-eafc33f2f318 > > umount /mnt/vmstore > > Best Regards, > Strahil Nikolov > > -- Adrian Quintero ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GXPLAFXIA6C74VAUXMJ62FVZIOMMY3HL/
[ovirt-users] Upgrade scenario to 4.4 for HCI Gluster
Hello, I saw from some mails in the list that the approach for upgrading from 4.3 to 4.4 will be similar to the 3.6 => 4.0 one. Reading the RHV 4.0 Self Hosted Engine Guide it seems it was necessary to have a second host, going through this: 5.4. Upgrading a RHEV-H-Based Self-Hosted Engine Environment https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html/self-hosted_engine_guide/upgrading_a_rhev-h-based_self-hosted_engine_environment and also https://www.ovirt.org/develop/release-management/features/sla/hosted-engine-migration-to-4-0.html upgrade process involved: - set global ha maintenance - install a new host (and set it as on hosted engine one) - migrate engine VM to this host and set the host as the SPM - create a backup with engine-backup, verify its contents and copy to the host in some directory - run the upgrade utility on the host to update the engine VM hosted-engine --upgrade-appliance this will create a backup floating disk of the engine vm disk for rollback purposes and override the existing engine disk with a new one where to deploy the new engine version applying also the restore from the engine-backup --> what are requirements for 4.4 engine VM and so free storage to have on engine storage domain? The engine-setup will be automatically executed on the new version engine VM - exit from global maintenance - update remaining hosts Is the above procedure the correct one that I can test on a 4.3.9 lab? The 3.6 -> 4.0 flow implied that a 4.0 host could run a 3.6 engine VM Because the backup disk operation is done by the current running engine itself. So it should be true also for 4.3 -> 4.4 and a 4.4. host should be able to run a 4.3 engine, correct? In case of single 4.3.9 ovirt-node-ng host HCI with Gluster, can I apply the upgrade in a similar way? Something like: - create engine-backup and copy over to the host - put host into global maintenace - shutdown all VMS, engine included - enable 4.4. repo - install new image-base 4.4 is this correct and I can use 4.3 and 4.4 image base versions or do I have to sort-of-scratch necessarily? because 4.3 host is based on el7 while 4.4 on el8... but perhaps on mage based system I have flexibility..? what version of gluster will it be applied? Incompatibilities with the current 4.3.9 one (version 6.8-1.el7) - reboot host - exit global maintenance and wait for engine vm to come up correctly - enter global maintenance again - run the upgrade utility on the host Or do I need at least temporarily a new server to use as the 4.4. host, or what will be the expected path? Thanks, Gianluca ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UR4IJEGRLIIOHZPUD44SK7BRYKM76BHB/
[ovirt-users] Re: oVirt 4.3.7 + Gluster 6.6 unsynced entries
On April 16, 2020 9:27:11 PM GMT+03:00, adrianquint...@gmail.com wrote: >Hi Strahil, >This is what method 2 came up with: > >[root@host1 ~]# getfattr -n trusted.glusterfs.pathinfo -e text >/rhev/data-center/mnt/glusterSD/192.168.0.59\:_vmstore/ >getfattr: Removing leading '/' from absolute path names ># file: rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore/ >trusted.glusterfs.pathinfo="( > > >)" > > >I will try method 1, but just want to make sure I am running it against >the correct file directory. >___ >Users mailing list -- users@ovirt.org >To unsubscribe send an email to users-le...@ovirt.org >Privacy Statement: https://www.ovirt.org/privacy-policy.html >oVirt Code of Conduct: >https://www.ovirt.org/community/about/community-guidelines/ >List Archives: >https://lists.ovirt.org/archives/list/users@ovirt.org/message/7377A4JQ54AYWBIVGJ6XJLG5THCGETH3/ Hey Adrian, Can you provide the output of the following: mount -t glusterfs -o aux-gfid-mount host1:vmstore /mnt/vmstore getfattr -n trusted.glusterfs.pathinfo -e text /mnt/vmstore/.gfid/5aeb168c-b8e3-4581-97f9-eafc33f2f318 umount /mnt/vmstore Best Regards, Strahil Nikolov ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/W3W6OOBP2D3FJDJJ64FKZVLHIFR6BZA4/
