On April 18, 2020 4:46:35 PM GMT+03:00, Adrian Quintero <[email protected]> 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 <[email protected]> >wrote: > >> On April 16, 2020 9:27:11 PM GMT+03:00, [email protected] >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="(<REPLICATE:vmstore-replicate-0> >> >> >><POSIX(/gluster_bricks/vmstore/vmstore):host2:/gluster_bricks/vmstore/vmstore/> >> >> >><POSIX(/gluster_bricks/vmstore/vmstore):host3:/gluster_bricks/vmstore/vmstore/> >> >> >><POSIX(/gluster_bricks/vmstore/vmstore):host1:/gluster_bricks/vmstore/vmstore/>)" >> > >> > >> >I will try method 1, but just want to make sure I am running it >against >> >the correct file directory. >> >_______________________________________________ >> >Users mailing list -- [email protected] >> >To unsubscribe send an email to [email protected] >> >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/[email protected]/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 -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/EXYIGWTA7BCD3GIQRUEZNPZIU7TW2QKD/
