gluster> volume info
Volume Name: vol00
Type: Distribute
Volume ID: 66a73e46-fabf-4cb3-b2b1-54b8f12dfc9c
Status: Started
Snapshot Count: 0
Number of Bricks: 3
Transport-type: tcp
Bricks:
Brick1: linux-acronis:/home/gvol
Brick2: linux-12sp5-1:/home/gvol
Brick3: linux-133:/home/gvol
Options Reconfigured:
performance.client-io-threads: on
nfs.disable: on
transport.address-family: inet
删除砖块成功:
gluster> volume remove-brick vol00 linux-12sp5-1:/home/gvol start
Running remove-brick with cluster.force-migration enabled can result in data corruption. It is safer to disable
this option so that files that receive writes during migration are not migrated.
Files that are not migrated can then be manually copied after the remove-brick commit operation.
Do you want to continue with your current cluster.force-migration settings? (y/n) y
volume remove-brick start: success
ID: 8e3b5343-ee45-421b-8ee9-10d12a1fb535
看状态
gluster> volume remove-brick vol00 linux-12sp5-1:/home/gvol status
也可以强力删除:
gluster> volume remove-brick vol00 linux-12sp5-1:/home/gvol force
Remove-brick force will not migrate files from the removed bricks, so they will no longer be available on the
volume.
Do you want to continue? (y/n) y
volume remove-brick commit force: success
gluster> volume info
Volume Name: vol00
Type: Distribute
Volume ID: 66a73e46-fabf-4cb3-b2b1-54b8f12dfc9c
Status: Started
Snapshot Count: 0
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: linux-acronis:/home/gvol
Brick2: linux-133:/home/gvol
Options Reconfigured:
performance.client-io-threads: on
nfs.disable: on
transport.address-family: inet