search for: tier1data

...pecific sequence or trick I need to follow? Currently, I am using the following command: [root at master2 ~]# systemctl stop glusterd.service [root at master2 ~]# ps aux | grep gluster root 2710138 14.1 0.0 2968372 216852 ? Ssl Jan27 170:27 /usr/sbin/glusterfsd -s master2 --volfile-id tier1data.master2.opt-tier1data2019-brick -p /var/run/gluster/vols/tier1data/master2-opt-tier1data2019-brick.pid -S /var/run/gluster/97da28e3d5c23317.socket --brick-name /opt/tier1data2019/brick -l /var/log/glusterfs/bricks/opt-tier1data2019-brick.log --xlator-option *-posix.glusterd-uuid=c1591bde-df1c-41b4-...

Hi There, We have a Gluster setup with three master nodes in replicated mode and one slave node with geo-replication. # gluster volume info Volume Name: tier1data Type: Replicate Volume ID: 93c45c14-f700-4d50-962b-7653be471e27 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: master1:/opt/tier1data2019/brick Brick2: master2:/opt/tier1data2019/brick Brick3: master3:/opt/tier1data2019/brick master1 | master2 |...

Hi All, I have run the following commands on master3, and that has added master3 to geo-replication. gluster system:: execute gsec_create gluster volume geo-replication tier1data drtier1data::drtier1data create push-pem force gluster volume geo-replication tier1data drtier1data::drtier1data stop gluster volume geo-replication tier1data drtier1data::drtier1data start Now I am able to start the geo-replication, but I am getting the same error. [2024-01-24 19:51:24.80892] I...

...?????, 26 ?????? 2024 ?. ? 18:07:59 ?. ???????+2, Anant Saraswat <anant.saraswat at techblue.co.uk> ??????: Hi All, I have run the following commands on master3, and that has added master3 to geo-replication. gluster system:: execute gsec_create gluster volume geo-replication tier1data drtier1data::drtier1data create push-pem force gluster volume geo-replication tier1data drtier1data::drtier1data stop gluster volume geo-replication tier1data drtier1data::drtier1data start Now I am able to start the geo-replication, but I am getting the same error. [2024-01-24 19:51:24.808...

...?????, 26 ?????? 2024 ?. ? 18:07:59 ?. ???????+2, Anant Saraswat <anant.saraswat at techblue.co.uk> ??????: Hi All, I have run the following commands on master3, and that has added master3 to geo-replication. gluster system:: execute gsec_create gluster volume geo-replication tier1data drtier1data::drtier1data create push-pem force gluster volume geo-replication tier1data drtier1data::drtier1data stop gluster volume geo-replication tier1data drtier1data::drtier1data start Now I am able to start the geo-replication, but I am getting the same error. [2024-01-24 19:51:24.808...

...stop-all-gluster-processes.sh script, I wanted to stop all gluster server-related processes on the server, but not to unmount the external gluster volume mounted on the server. However, running stop-all-gluster-processes.sh unmounted the dc.local:/docker_config volume from the server. /dev/mapper/tier1data 6.1T 4.7T 1.4T 78% /opt/tier1data/brick dc.local:/docker_config 100G 81G 19G 82% /opt/docker_config Do you think stop-all-gluster-processes.sh should unmount the fuse mount? Thanks, Anant ________________________________ From: Gluster-users <gluster-users-bounces at...

...stop-all-gluster-processes.sh script, I wanted to stop all gluster server-related processes on the server, but not to unmount the external gluster volume mounted on the server. However, running stop-all-gluster-processes.sh unmounted the dc.local:/docker_config volume from the server. /dev/mapper/tier1data 6.1T 4.7T 1.4T 78% /opt/tier1data/brick dc.local:/docker_config 100G 81G 19G 82% /opt/docker_config Do you think stop-all-gluster-processes.sh should unmount the fuse mount? Thanks, Anant ________________________________ From: Gluster-users <gluster-users-bounces at...

...op-all-gluster-processes.sh script, I wanted to stop all gluster server-related processes on the server, but not to unmount the external gluster volume mounted on the server. However, running stop-all-gluster-processes.sh unmounted the dc.local:/docker_config volume from the server. /dev/mapper/tier1data ? ? ? ? ? ? ? ? ? 6.1T ?4.7T ?1.4T ?78% /opt/tier1data/brick dc.local:/docker_config ?100G ? 81G ? 19G ?82% /opt/docker_config Do you think stop-all-gluster-processes.sh should unmount the fuse mount? Thanks, Anant From:?Gluster-users <mailto:gluster-users-bounces at gluster.org> on...

...e stop-all-gluster-processes.sh script, I wanted to stop all gluster server-related processes on the server, but not to unmount the external gluster volume mounted on the server. However, running stop-all-gluster-processes.sh unmounted the dc.local:/docker_config volume from the server. /dev/mapper/tier1data ? ? ? ? ? ? ? ? ? 6.1T ?4.7T ?1.4T ?78% /opt/tier1data/brickdc.local:/docker_config ?100G ? 81G ? 19G ?82% /opt/docker_config Do you think stop-all-gluster-processes.sh should unmount the fuse mount? Thanks,AnantFrom:?Gluster-users <gluster-users-bounces at gluster.org> on behalf of Strahil N...

I think the service that shutdowns the bricks on EL systems is something like this - right now I don't have access to my systems to check but you can extract the rpms and see it: https://bugzilla.redhat.com/show_bug.cgi?id=1022542#c4 Best Regards,Strahil Nikolov On Wed, Feb 7, 2024 at 19:51, Ronny Adsetts<ronny.adsetts at amazinginternet.com> wrote: ________ Community Meeting

...stop-all-gluster-processes.sh script, I wanted to stop all gluster server-related processes on the server, but not to unmount the external gluster volume mounted on the server. However, running stop-all-gluster-processes.sh unmounted the dc.local:/docker_config volume from the server. /dev/mapper/tier1data 6.1T 4.7T 1.4T 78% /opt/tier1data/brick dc.local:/docker_config 100G 81G 19G 82% /opt/docker_config Do you think stop-all-gluster-processes.sh should unmount the fuse mount? Thanks, Anant ________________________________ From: Gluster-users <gluster-users-bounces at...

...esses.sh script, I wanted to stop all gluster server-related processes on the server, but not to unmount the external gluster volume mounted on the server. However, running stop-all-gluster-processes.sh unmounted the dc.local:/docker_config volume from the server. > > > > /dev/mapper/tier1data ? ? ? ? ? ? ? ? ? 6.1T ?4.7T ?1.4T ?78% /opt/tier1data/brick > > dc.local:/docker_config ?100G ? 81G ? 19G ?82% /opt/docker_config > > > > Do you think stop-all-gluster-processes.sh should unmount the fuse mount? > > > > Thanks, > > Anant > ___________...

...n't create any issues. In our setup, when we stop Gluster on any of the nodes, we mostly get the error 'Transport endpoint is not connected' on the clients. When we run the commands to check the connected clients on the Gluster server, we get the following error: gluster volume status tier1data clients FAILED: Commit failed on master1. Error: Unable to decode brick op response. Could anyone recommend a potential solution for this? Thanks, Anant Anant Saraswat DevOps Lead IT | Technology Blueprint Ltd. [mobilePhone] +44-8450047142 (5020)<tel:+44-8450047142%20(5020)> | +91-98187...

...gt; In our setup, when we stop Gluster on any of the nodes, we mostly get the > error 'Transport endpoint is not connected' on the clients. When we run the > commands to check the connected clients on the Gluster server, we get the > following error: > > gluster volume status tier1data clients > FAILED: Commit failed on master1. Error: Unable to decode brick op > response. > > Could anyone recommend a potential solution for this? > > Thanks, > Anant > > Anant Saraswat > > DevOps Lead > > IT | Technology Blueprint Ltd. > [image: mobilePhon...