Thank you all for this. Unfortunately I wasn't able to try this. In my
attempt to change the brick name, I noticed I'm on Gluster 3.13 (Not a
typo) . So I proceeded to update to 6.10 then from there, to 9.4. To
6.10 it went fine however from 6.10 to 9.4 everything blew up. I got a
Hi Tom,
I think you could use the replace-brick sub-command; like: "gluster volume
replace-brick :/bricks/0/gv01
:/bricks/0/abc-gv01 commit force"
see;
https://docs.gluster.org/en/latest/Administrator-Guide/Managing-Volumes/#replace-brick
Kind regards,
Olaf
Op di 4 jan. 2022 om 12:50
Hi,
I use the sequence below to move a brick to a different peer. I assume it also
works for renaming a brick (just put peer01 = peer02 = whateveryourpeeris). I
used this on a distributed-only volume (no replication) running glusterfs 9.3.
Please note that I didn't to extensive tests and I
