On 11/06/19 9:11 PM, Alan Orth wrote:
No, all these very steps are 'codified' into the `replace brick commit force` command via https://review.gluster.org/#/c/glusterfs/+/10076/ and https://review.gluster.org/#/c/glusterfs/+/10448/. You can see the commit messages of these 2 patches for more details. You can play around with most of these commands in a 1 node setup if you want to convince yourself that they work. There is no need to form a cluster. [root@tuxpad glusterfs]# gluster v create testvol replica 3 127.0.0.2:/home/ravi/bricks/brick{1..3} force [root@tuxpad glusterfs]# gluster v start testvol [root@tuxpad glusterfs]# mount -t glusterfs 127.0.0.2:testvol /mnt/fuse_mnt/ [root@tuxpad glusterfs]# touch /mnt/fuse_mnt/FILE [root@tuxpad glusterfs]# ll /home/ravi/bricks/brick*/FILE -rw-r--r--. 2 root root 0 Jun 11 21:55 /home/ravi/bricks/brick1/FILE -rw-r--r--. 2 root root 0 Jun 11 21:55 /home/ravi/bricks/brick2/FILE -rw-r--r--. 2 root root 0 Jun 11 21:55 /home/ravi/bricks/brick3/FILE [root@tuxpad glusterfs]# gluster v replace-brick testvol 127.0.0.2:/home/ravi/bricks/brick3 127.0.0.2:/home/ravi/bricks/brick3_new commit force volume replace-brick: success: replace-brick commit force operation successful [root@tuxpad glusterfs]# ll /home/ravi/bricks/brick3_new/FILE -rw-r--r--. 2 root root 0 Jun 11 21:55 /home/ravi/bricks/brick3_new/FILE Why don't you send a patch to update the doc for replace-brick? I'd be happy to review it. ;-)HTH, Ravi
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users