Displaying 2 results from an estimated 2 matches for "brick3_new".
2019 Jun 12
1
Proper command for replace-brick on distribute–replicate?
...w-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 at 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 at 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 d...
2019 Jun 11
1
Proper command for replace-brick on distribute–replicate?
Dear list,
In a recent discussion on this list Ravi suggested that the documentation
for replace-brick? was out of date. For a distribute?replicate volume the
documentation currently says that we need to kill the old brick's PID,
create a temporary empty directory on the FUSE mount, check the xattrs,
replace-brick with commit force.
Is all this still necessary? I'm running Gluster 5.6 on