Collation of commonly used glusterfs commands

# 1  Start stop and start-up 
systemctl start  glusterd.service
systemctl enable glusterd.service
systemctl status glusterd.service

#2  Add... To the storage pool / Remove the server node 
gluster peer probe <SERVER>
gluster peer detach <SERVER>
 Be careful , When removing nodes , You need to set the on this node in advance Brick remove .

# 3 View the basic status of all nodes （ Exclude this node ）：
gluster peer status

# 4  mount glusterfs
mount -t glusterfs <SERVER>:/<VOLNAME><MOUNTDIR>

#5  establish / start-up / stop it / Delete volume 
gluster volume create <NEW-VOLNAME>[stripe <COUNT> \
    | replica <COUNT>] \
    [transport [tcp | rdma | tcp,rdma]] \
    <NEW-BRICK1> <NEW-BRICK2> \
    <NEW-BRICK3> <NEW-BRICK4>...

gluster volume start <VOLNAME>
gluster volume stop <VOLNAME>
gluster volume delete <VOLNAME>
 Be careful , The prerequisite for deleting a volume is to stop the volume first .

# 6  View volume information 
gluster volume list    # List all the volumes in the cluster ：
gluster volume info [all]    # View the volume information in the cluster ：
gluster volume status [all]    # View the volume status in the cluster ：
gluster volume status <VOLNAME> [detail| clients | mem | inode | fd] 

# 7  configure volumes 
gluster volume set <VOLNAME> <OPTION> <PARAMETER>

# 8   Expand volume 
gluster volume add-brick <VOLNAME> <NEW-BRICK>
> In the case of a replicated volume , Then every time you add Brick The number must be replica Integer multiple .

# 9  Shrink roll 
## 9.1  First, migrate the data to other available Brick, After the migration, the Brick remove ：
gluster volume remove-brick <VOLNAME> <BRICK> start
> In execution start after , have access to status Command to view the removal progress ：
gluster volume remove-brick <VOLNAME> <BRICK> status

## 9.2 No data migration , Delete the Brick：
gluster volume remove-brick <VOLNAME> <BRICK> commit
> Be careful , If it's a copy volume or a striped volume , Each time you remove Brick The number must be replica perhaps stripe Integer multiple .

# 10  Migrating volumes 
> Use start The command starts the migration 
> During migration , have access to pause Command to pause migration ：
			 have access to abort Command to terminate the migration ：
			 have access to status Command to view the migration progress ：
> At the end of the data migration , perform commit Order to proceed Brick Replace ：
gluster volume replace-brick <VOLNAME> <BRICK> <NEW-BRICK> start
gluster volume replace-brick <VOLNAME> <BRICK> <NEW-BRICK> pause
gluster volume replace-brick <VOLNAME> <BRICK> <NEW-BRICK> abort
gluster volume replace-brick <VOLNAME> <BRICK> <NEW-BRICK> status
gluster volume replace-brick <VOLNAME> <BRICK> <NEW-BRICK> commit

# 11  Rebalance the volume 
 Do not migrate data ：
gluster volume rebalance <VOLNAME> lay-outstart
gluster volume rebalance <VOLNAME> start
gluster volume rebalance <VOLNAME> startforce
gluster volume rebalance <VOLNAME> status
gluster volume rebalance <VOLNAME> stop

# 12  Disk quota 
 Turn on / Turn off system quotas ：
gluster volume quota <VOLNAME> enable | disable
 Set directory quota ：
gluster volume quota <VOLNAME> limit-usage <DIR> <VALUE>
 Look at the quota ：
gluster volume quota <VOLNAME> list [<DIR>]

# 13  Regional replication （geo-replication）：
gluster volume geo-replication <MASTER> <SLAVE> start | status | stop

# 14 IO Information view ：
gluster volume profile <VOLNAME> start | info | stop

# 15 Top monitor ：
>Top The command allows you to view Brick Performance of , for example ：read,write, file open calls, file read calls, file write calls, directory opencalls, and directory real calls. All views can be set top Count , Default 100.

gluster volume top <VOLNAME> open[brick <BRICK>] [list-cnt <COUNT>]
> among ,open Can be replaced with read, write, opendir, readdir etc. .

gluster volume top <VOLNAME> read-perf [bs <BLOCK-SIZE> count <COUNT>] [brick <BRICK>] [list-cnt <COUNT>]
> among ,read-perf Can be replaced with write-perf etc. .