Hello!
I'm playing with gluster fuse client.
And this is newbie question.
I have gluster 3.7.13, volume , which contains 3 bricks:
[root@father bricks]# gluster volume info pool
Volume Name: pool
Type: Replicate
Volume ID: 6748e47c-4a2e-4a80-a42d-61b6917f4a41
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: father:/wall/pool/brick
Brick2: son:/wall/pool/brick
Brick3: spirit:/wall/pool/brick
Than I mount this pool over fuse:
[root@father ~]# mount -t glusterfs localhost:/pool /root/gluster/
[root@father ~]# cp /var/local/files/gstatus-0.64-3.el7.x86_64.rpm
/root/gluster/
OK, file is here:
[root@father ~]# ls /root/gluster/gs*
/root/gluster/gstatus-0.64-3.el7.x86_64.rpm
Than I'm going to simulate some problem like accidental removal and
remove file directly from brick:
[root@father ~]# rm /wall/pool/brick/gstatus-0.64-3.el7.x86_64.rpm
rm: удалить обычный файл «/wall/pool/brick/gstatus-0.64-3.el7.x86_64.rpm»? y
and ... there is no such file listed...
[root@father ~]# ls /root/gluster/gs*
ls: невозможно получить доступ к /root/gluster/gs*: Нет такого файла или
каталога
[root@father ~]# LANG=C ls /root/gluster/gs*
ls: cannot access /root/gluster/gs*: No such file or directory
[root@father ~]#
But, if I call this file by full name, then it is here and even is
replicated to brick
[root@father ~]# LANG=C ls /root/gluster/gstatus-0.64-3.el7.x86_64.rpm
/root/gluster/gstatus-0.64-3.el7.x86_64.rpm
[root@father bricks]# ls /wall/pool/brick/gstatus-0.64-3.el7.x86_64.rpm
/wall/pool/brick/gstatus-0.64-3.el7.x86_64.rpm
[root@father bricks]#
Is this expected behaviour?
Thank you!
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
