search for: nodirectwritedata

...-server=sg --volfile-id=/gvol0 --fuse-mountopts=noatime /mnt/glusterfs root 2379 2052 0 2022 ? 00:00:00 /usr/bin/python3 /usr/sbin/glustereventsd --pid-file /var/run/glustereventsd.pid root 5884 1 5 2022 ? 18-16:08:53 /usr/sbin/glusterfsd -s br --volfile-id gvol0.br.nodirectwritedata-gluster-gvol0 -p /var/run/gluster/vols/gvol0/br-nodirectwritedata-gluster-gvol0.pid -S /var/run/gluster/61df1d4e1c65300e.socket --brick-name /nodirectwritedata/gluster/gvol0 -l /var/log/glusterfs/bricks/nodirectwritedata-gluster-gvol0.log --xlator-option *-posix.glusterd-uuid=11e528b0-8c69-4b5d-82e...

...t voisonics.com<mailto:dcunningham at voisonics.com>> wrote: We've tried to remove "sg" from the cluster so we can re-install the GlusterFS node on it, but the following command run on "br" also gives a timeout error: gluster volume remove-brick gvol0 replica 1 sg:/nodirectwritedata/gluster/gvol0 force How can we tell "br" to just remove "sg" without trying to contact it? On Fri, 24 Feb 2023 at 10:31, David Cunningham <dcunningham at voisonics.com<mailto:dcunningham at voisonics.com>> wrote: Hello, We have a cluster with two nodes, "sg&...

Hi David, It seems that I have misread your quorum options, so just ignore that from my previous e-mail. Best Regards, Strahil NikolovOn Dec 27, 2019 15:38, Strahil <hunter86_bg at yahoo.com> wrote: > > Hi David, > > Gluster supports live rolling upgrade, so there is no need to redeploy at all - but the migration notes should be checked as some features must be disabled first.