Hide Forgot
A work around for this can be that - If the brick count is equal the count of the bricks to be removed, then we can report an error saying this is not a permitted command, a better option is to delete the volume.
gluster> volume info Volume Name: repl Type: Distributed-Replicate Status: Started Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: booradley:/home/export/9 Brick2: booradley:/home/export/10 Brick3: booradley:/home/export/11 Brick4: booradley:/home/export/12 gluster> volume remove-brick repl booradley:/home/export/9 booradley:/home/export/10 Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y Remove Brick successful gluster> volume remove-brick repl booradley:/home/export/12 booradley:/home/export/11 Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y Remove Brick unsuccessful gluster> volume info Volume Name: repl Type: Replicate Status: Started Number of Bricks: 0 Transport-type: tcp Please note that, even though cli reported remove-brick as unsuccessful, number of bricks is zero. Also, as expected no glusterfs server processes were started. But looking at glusterfs client volume file, it still consisted of a replicate setup of two clients. Probably we should just indicate the user that since these were the last pair of bricks remaining, it does not make sense to remove them and hence the operation is not permissible. gluster> volume add-brick repl booradley:/home/export/5 booradley:/home/export/6/ Add Brick successful gluster> volume info Volume Name: repl Type: Replicate Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: booradley:/home/export/5 Brick2: booradley:/home/export/6 regards, Raghavendra.
PATCH: http://patches.gluster.com/patch/5995 in master (mgmt/glusterd: error out if remove-brick comes for final bricks)
It is fixed. If the last bricks are tried to be removed, it gives an error if the last bricks of the volume are tried to be removed. root@bigbang:/home/raghu# gluster volume remove-brick mirror bigbang:/e/glusterfs/export/export bigbang:/e/glusterfs/export/export1 Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y Remove Brick successful root@bigbang:/home/raghu# gluster volume info Volume Name: mirror Type: Replicate Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: bigbang:/d/glusterfs/export/export Brick2: bigbang:/d/glusterfs/export/export1 root@bigbang:/home/raghu# gluster volume remove-brick mirror bigbang:/d/glusterfs/export/export bigbang:/d/glusterfs/export/export1 Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y Deleting all the bricks of the volume is not allowed