Striping Across Four Storage Nodes With GlusterFS 3.2.x On CentOS 6.3

This tutorial exists for these OS versions

On this page

  1. 1 Preliminary Note
  2. 2 Enable Additional Repositories
  3. 3 Setting Up The GlusterFS Servers

This tutorial shows how to do data striping (segmentation of logically sequential data, such as a single file, so that segments can be assigned to multiple physical devices in a round-robin fashion and thus written concurrently) across four single storage servers (running CentOS 6.3) with GlusterFS. The client system (CentOS 6.3 as well) will be able to access the storage as if it was a local filesystem. GlusterFS is a clustered file-system capable of scaling to several peta-bytes. It aggregates various storage bricks over Infiniband RDMA or TCP/IP interconnect into one large parallel network file system. Storage bricks can be made of any commodity hardware such as x86_64 servers with SATA-II RAID and Infiniband HBA.

Please note that this kind of storage doesn't provide any high-availability/fault tolerance features, as would be the case with replicated storage.

I do not issue any guarantee that this will work for you!


1 Preliminary Note

In this tutorial I use five systems, four servers and a client:

  • IP address (server)
  • IP address (server)
  • IP address (server)
  • IP address (server)
  • IP address (client)

All five systems should be able to resolve the other systems' hostnames. If this cannot be done through DNS, you should edit the /etc/hosts file so that it looks as follows on all five systems:

vi /etc/hosts   localhost localhost.localdomain localhost4 localhost4.localdomain4     server1     server2     server3     server4     client1

::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

(It is also possible to use IP addresses instead of hostnames in the following setup. If you prefer to use IP addresses, you don't have to care about whether the hostnames can be resolved or not.)


2 Enable Additional Repositories

First we import the GPG keys for software packages:

rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY*

Then we enable the EPEL6 repository on our CentOS systems:

rpm --import
cd /tmp
rpm -ivh epel-release-6-7.noarch.rpm
yum install yum-priorities

Edit /etc/yum.repos.d/epel.repo...

vi /etc/yum.repos.d/epel.repo

... and add the line priority=10 to the [epel] section:

name=Extra Packages for Enterprise Linux 6 - $basearch


3 Setting Up The GlusterFS Servers

GlusterFS is available as a package for EPEL, therefore we can install it as follows:

yum install glusterfs-server

Create the system startup links for the Gluster daemon and start it:

chkconfig --levels 235 glusterd on
/etc/init.d/glusterd start

The command

glusterfsd --version

should now show the GlusterFS version that you've just installed (3.2.7 in this case):

[root@server1 ~]# glusterfsd --version
glusterfs 3.2.7 built on Jun 11 2012 13:22:28
Repository revision: git://
Copyright (c) 2006-2011 Gluster Inc. <>
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.
[root@server1 ~]#

If you use a firewall, ensure that TCP ports 111, 24007, 24008, 24009-(24009 + number of bricks across all volumes) are open on,,, and

Next we must add,, and to the trusted storage pool (please note that I'm running all GlusterFS configuration commands from, but you can as well run them from or or because the configuration is repliacted between the GlusterFS nodes - just make sure you use the correct hostnames or IP addresses):

On, run

gluster peer probe
gluster peer probe
gluster peer probe

Output should be as follows:

[root@server1 ~]# gluster peer probe
Probe successful
[root@server1 ~]#

The status of the trusted storage pool should now be similar to this:

gluster peer status
[root@server1 ~]# gluster peer status
Number of Peers: 3
Uuid: 600ff607-f7fd-43f6-af8d-419df703376d
State: Peer in Cluster (Connected)
Uuid: 1d6a5f3f-c2dd-4727-a050-0431772cc381
State: Peer in Cluster (Connected)
Uuid: 0bd9d445-0b5b-4a91-be6f-02b13c41d5d6
State: Peer in Cluster (Connected)
[root@server1 ~]#

Next we create the striped share named testvol (please note that the number of stripes is equal to the number of servers in this case) on,,, and in the /data directory (this will be created if it doesn't exist):

gluster volume create testvol stripe 4 transport tcp
[root@server1 ~]# gluster volume create testvol stripe 4 transport tcp
Creation of volume testvol has been successful. Please start the volume to access data.
[root@server1 ~]#

Start the volume:

gluster volume start testvol

It is possible that the above command tells you that the action was not successful:

[root@server1 ~]# gluster volume start testvol
Starting volume testvol has been unsuccessful
[root@server1 ~]#

In this case you should check the output of...

netstat -tap | grep glusterfsd

on both servers.

If you get output like this...

[root@server1 ~]# netstat -tap | grep glusterfsd
tcp        0      0 *:24009                     *:*                         LISTEN      1365/glusterfsd
tcp        0      0 localhost:1023              localhost:24007             ESTABLISHED 1365/glusterfsd
tcp        0      0    ESTABLISHED 1365/glusterfsd
[root@server1 ~]#

... everything is fine, but if you don't get any output...

[root@server2 ~]# netstat -tap | grep glusterfsd
[root@server2 ~]#
[root@server3 ~]# netstat -tap | grep glusterfsd
[root@server3 ~]#
[root@server4 ~]# netstat -tap | grep glusterfsd
[root@server4 ~]#

... restart the GlusterFS daemon on the corresponding server (,, and in this case):

/etc/init.d/glusterfsd restart

Then check the output of...

netstat -tap | grep glusterfsd

... again on these servers - it should now look like this:

[root@server2 ~]# netstat -tap | grep glusterfsd
tcp        0      0 *:24009                 *:*                     LISTEN      1152/glusterfsd
tcp        0      0 localhost.localdom:1018 localhost.localdo:24007 ESTABLISHED 1152/glusterfsd
[root@server2 ~]#

[root@server3 ~]# netstat -tap | grep glusterfsd
tcp        0      0 *:24009                 *:*                     LISTEN      1311/glusterfsd
tcp        0      0 localhost.localdom:1018 localhost.localdo:24007 ESTABLISHED 1311/glusterfsd
[root@server3 ~]#

[root@server4 ~]# netstat -tap | grep glusterfsd
tcp        0      0 *:24009                 *:*                     LISTEN      1297/glusterfsd
tcp        0      0 localhost.localdom:1019 localhost.localdo:24007 ESTABLISHED 1297/glusterfsd
[root@server4 ~]#

Now back to

You can check the status of the volume with the command

gluster volume info
[root@server1 ~]# gluster volume info
Volume Name: testvol
Type: Stripe
Status: Started
Number of Bricks: 4
Transport-type: tcp
[root@server1 ~]#

By default, all clients can connect to the volume. If you want to grant access to (= only, run:

gluster volume set testvol auth.allow

Please note that it is possible to use wildcards for the IP addresses (like 192.168.*) and that you can specify multiple IP addresses separated by comma (e.g.,

The volume info should now show the updated status:

gluster volume info
[root@server1 ~]# gluster volume info
Volume Name: testvol
Type: Stripe
Status: Started
Number of Bricks: 4
Transport-type: tcp
Options Reconfigured:
[root@server1 ~]#
Share this page:

0 Comment(s)