Configure Storage Clustering with GlusterFS.
For example, Create a Distributed + Replication volume with 6 Nodes.
Also Configure Arbiter Volume in order to avoid Split Brain.

+----------------------+          |          +----------------------+
| [GlusterFS Server#1] |10.0.0.51 | 10.0.0.54| [GlusterFS Server#4] |
|   glus01.srv.local   +----------+----------+   glus04.srv.local   |
|                      |          |          |                      |
+----------------------+          |          +----------------------+
                                  |
+----------------------+          |          +----------------------+
| [GlusterFS Server#2] |10.0.0.52 | 10.0.0.55| [GlusterFS Server#5] |
|   glus02.srv.local   +----------+----------+   glus05.srv.local   |
|                      |          |          |                      |
+----------------------+          |          +----------------------+
                                  |
+----------------------+          |          +----------------------+
| [GlusterFS Server#3] |10.0.0.53 | 10.0.0.56| [GlusterFS Server#6] |
|   glus03.srv.local   +----------+----------+   glus06.srv.local   |
|                      |                     |                      |
+----------------------+                     +----------------------+
           ⇑                                             ⇑
     file1, file3 ...                             file2, file4 ...

It is strongly recommended to use partitions for GlusterFS volumes that are different from the / partition.
On this example, it shows settings on the environment that all nodes has [sdb1] and mount it to [/glusterfs].

[1] Install GlusterFS Server on All Nodes, refer to here.

[2] Create a Directory for GlusterFS Volume on all Nodes.

root@glus01:~# mkdir -p /glusterfs/dist-replica

[3] Configure Clustering like follows on a node. (it’s OK on any node)

# probe nodes
root@glus01:~# gluster peer probe glus02
peer probe: success.
root@glus01:~# gluster peer probe glus03
peer probe: success.
root@glus01:~# gluster peer probe glus04
peer probe: success.
root@glus01:~# gluster peer probe glus05
peer probe: success.
root@glus01:~# gluster peer probe glus06
peer probe: success.
# confirm status
root@node01:~# gluster peer status
Number of Peers: 5

Hostname: glus02
Uuid: f1c4ce91-1b08-45f7-84e7-6549a85071fd
State: Peer in Cluster (Connected)

Hostname: glus03
Uuid: 075c4737-17fb-4476-9668-02dab9315d85
State: Peer in Cluster (Connected)

Hostname: glus04
Uuid: 1a80e3a9-c07d-4bf1-a008-ab208a6c1196
State: Peer in Cluster (Connected)

Hostname: glus05
Uuid: 6e72d379-e122-4091-97a4-c4908603f737
State: Peer in Cluster (Connected)

Hostname: glus06
Uuid: 1d7cbd06-eccd-4f5b-8edc-62b1806c89e1
State: Peer in Cluster (Connected)

# create volume
root@glus01:~# gluster volume create vol_dist-replica replica 3 arbiter 1 transport tcp \
glus01:/glusterfs/dist-replica \
glus02:/glusterfs/dist-replica \
glus03:/glusterfs/dist-replica \
glus04:/glusterfs/dist-replica \
glus05:/glusterfs/dist-replica \
glus06:/glusterfs/dist-replica
volume create: vol_dist-replica: success: please start the volume to access data
# start volume
root@glus01:~# gluster volume start vol_dist-replica
volume start: vol_dist-replica: success
# confirm volume info
root@glus01:~# gluster volume info

Volume Name: vol_dist-replica
Type: Distributed-Replicate
Volume ID: 1debcb54-363f-4653-9c38-248a3d4d443e
Status: Started
Snapshot Count: 0
Number of Bricks: 2 x (2 + 1) = 6
Transport-type: tcp
Bricks:
Brick1: glus01:/glusterfs/dist-replica
Brick2: glus02:/glusterfs/dist-replica
Brick3: glus03:/glusterfs/dist-replica (arbiter)
Brick4: glus04:/glusterfs/dist-replica
Brick5: glus05:/glusterfs/dist-replica
Brick6: glus06:/glusterfs/dist-replica (arbiter)
Options Reconfigured:
transport.address-family: inet
storage.fips-mode-rchecksum: on
nfs.disable: on
performance.client-io-threads: off

[4] To mount GlusterFS volume on Client Hosts, refer to here.