oVirt 4.3.7 + Gluster 6.6 unsynced entries
Hello, I am having the following issue, it has been a few days and healing never finishes, any ideas on how to fix the unsynced entries? [root@host1 vmstore]# gluster vol heal vmstore info --------------------------------------------------- Brick host1:/gluster_bricks/vmstore/vmstore <gfid:5aeb168c-b8e3-4581-97f9-eafc33f2f318> <gfid:9a7483d9-0d68-4fcd-89b7-d281f6132506> <gfid:a3830550-5158-4cf9-af15-19faf5e51db0> Status: Connected Number of entries: 3 Brick host2:/gluster_bricks/vmstore/vmstore /.shard/9dbd7ab9-3d1c-4eed-908e-852eec1ce3b1.1240 /.shard/9dbd7ab9-3d1c-4eed-908e-852eec1ce3b1.1241 /.shard/9dbd7ab9-3d1c-4eed-908e-852eec1ce3b1.1242 Status: Connected Number of entries: 3 host3:/gluster_bricks/vmstore/vmstore Status: Connected Number of entries: 0 --------------------------------------------------- Thanks, Adrian
On April 16, 2020 5:13:21 PM GMT+03:00, adrianquintero@gmail.com wrote:
Hello, I am having the following issue, it has been a few days and healing never finishes, any ideas on how to fix the unsynced entries?
[root@host1 vmstore]# gluster vol heal vmstore info --------------------------------------------------- Brick host1:/gluster_bricks/vmstore/vmstore <gfid:5aeb168c-b8e3-4581-97f9-eafc33f2f318> <gfid:9a7483d9-0d68-4fcd-89b7-d281f6132506> <gfid:a3830550-5158-4cf9-af15-19faf5e51db0> Status: Connected Number of entries: 3
Brick host2:/gluster_bricks/vmstore/vmstore /.shard/9dbd7ab9-3d1c-4eed-908e-852eec1ce3b1.1240 /.shard/9dbd7ab9-3d1c-4eed-908e-852eec1ce3b1.1241 /.shard/9dbd7ab9-3d1c-4eed-908e-852eec1ce3b1.1242 Status: Connected Number of entries: 3
host3:/gluster_bricks/vmstore/vmstore Status: Connected Number of entries: 0 ---------------------------------------------------
Thanks,
Adrian _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/CIR4DW6LBW6GUN...
Hey Adrian, You can find the file name via https://docs.gluster.org/en/latest/Troubleshooting/gfid-to-path/ (I use method 2 , mounted on /mnt) Once you have the file , you can sync the file with newest data in it. I guess it's a '.meta' type of file, but let's see. Best Regards, Strahil Nikolov
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.
On April 16, 2020 9:27:11 PM GMT+03:00, adrianquintero@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="(<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 -- users@ovirt.org To unsubscribe send an email to users-leave@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/7377A4JQ54AYWB...
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
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 <hunter86_bg@yahoo.com> wrote:
On April 16, 2020 9:27:11 PM GMT+03:00, adrianquintero@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="(<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 -- users@ovirt.org To unsubscribe send an email to users-leave@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/7377A4JQ54AYWB...
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
On April 18, 2020 4:46:35 PM GMT+03:00, Adrian Quintero <adrianquintero@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 <hunter86_bg@yahoo.com> wrote:
On April 16, 2020 9:27:11 PM GMT+03:00, adrianquintero@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="(<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 -- users@ovirt.org To unsubscribe send an email to users-leave@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/7377A4JQ54AYWB...
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
ah ok.. want me to do it on any of the hosts? On Sat, Apr 18, 2020 at 10:34 AM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
On April 18, 2020 4:46:35 PM GMT+03:00, Adrian Quintero < adrianquintero@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 <hunter86_bg@yahoo.com> wrote:
On April 16, 2020 9:27:11 PM GMT+03:00, adrianquintero@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="(<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 -- users@ovirt.org To unsubscribe send an email to users-leave@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/7377A4JQ54AYWB...
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
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="(<REPLICATE:vmstore-replicate-0> <POSIX(/gluster_bricks/vmstore/vmstore):host3:/gluster_bricks/vmstore/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6> <POSIX(/gluster_bricks/vmstore/vmstore):host2:/gluster_bricks/vmstore/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6> <POSIX(/gluster_bricks/vmstore/vmstore):host1:/gluster_bricks/vmstore/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6>)" Thanks, On Sat, Apr 18, 2020 at 10:44 AM Adrian Quintero <adrianquintero@gmail.com> wrote:
ah ok.. want me to do it on any of the hosts?
On Sat, Apr 18, 2020 at 10:34 AM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
On April 18, 2020 4:46:35 PM GMT+03:00, Adrian Quintero < adrianquintero@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 <hunter86_bg@yahoo.com> wrote:
On April 16, 2020 9:27:11 PM GMT+03:00, adrianquintero@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="(<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 -- users@ovirt.org To unsubscribe send an email to users-leave@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/7377A4JQ54AYWB...
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
On April 18, 2020 5:58:03 PM GMT+03:00, Adrian Quintero <adrianquintero@gmail.com> 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="(<REPLICATE:vmstore-replicate-0> <POSIX(/gluster_bricks/vmstore/vmstore):host3:/gluster_bricks/vmstore/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6> <POSIX(/gluster_bricks/vmstore/vmstore):host2:/gluster_bricks/vmstore/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6> <POSIX(/gluster_bricks/vmstore/vmstore):host1:/gluster_bricks/vmstore/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6>)"
Thanks,
On Sat, Apr 18, 2020 at 10:44 AM Adrian Quintero <adrianquintero@gmail.com> wrote:
ah ok.. want me to do it on any of the hosts?
On Sat, Apr 18, 2020 at 10:34 AM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
On April 18, 2020 4:46:35 PM GMT+03:00, Adrian Quintero < adrianquintero@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 <hunter86_bg@yahoo.com> wrote:
On April 16, 2020 9:27:11 PM GMT+03:00, adrianquintero@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="(<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 -- users@ovirt.org To unsubscribe send an email to users-leave@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:
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
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7377A4JQ54AYWB... 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
Not sure if this is what is needed, as I still cant find the virtual directory .gfid. [root@host1 ~]# getfattr -n glusterfs.gfid.string /mnt/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6 getfattr: Removing leading '/' from absolute path names # file: mnt/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6 glusterfs.gfid.string="cf395203-bb5a-4ca2-9641-78457b502ba8" Thanks, Adrian On Sat, Apr 18, 2020 at 2:51 PM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
On April 18, 2020 5:58:03 PM GMT+03:00, Adrian Quintero < adrianquintero@gmail.com> 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="(<REPLICATE:vmstore-replicate-0>
<POSIX(/gluster_bricks/vmstore/vmstore):host3:/gluster_bricks/vmstore/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6>
<POSIX(/gluster_bricks/vmstore/vmstore):host2:/gluster_bricks/vmstore/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6>
<POSIX(/gluster_bricks/vmstore/vmstore):host1:/gluster_bricks/vmstore/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6>)"
Thanks,
On Sat, Apr 18, 2020 at 10:44 AM Adrian Quintero <adrianquintero@gmail.com> wrote:
ah ok.. want me to do it on any of the hosts?
On Sat, Apr 18, 2020 at 10:34 AM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
On April 18, 2020 4:46:35 PM GMT+03:00, Adrian Quintero < adrianquintero@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 <hunter86_bg@yahoo.com> wrote:
On April 16, 2020 9:27:11 PM GMT+03:00, adrianquintero@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="(<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 -- users@ovirt.org >To unsubscribe send an email to users-leave@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/7377A4JQ54AYWB...
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
-- Adrian Quintero
participants (3)
-
Adrian Quintero -
adrianquintero＠gmail.com
-
Strahil Nikolov