Cheap VPS & Xen Server

Residential Proxy Network - Hourly & Monthly Packages

Creating An NFS-Like Standalone Storage Server With GlusterFS On Mandriva 2010.0


This tutorial shows how to set up a standalone storage server on Mandriva 2010.0. Instead of NFS, I will use GlusterFS here. The client system 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.

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

 

1 Preliminary Note

In this tutorial I use two systems, a server and a client:

  • server1.example.com: IP address 192.168.0.100 (server)
  • client1.example.com: IP address 192.168.0.101 (client)

Both systems should be able to resolve the other system’s hostname. If this cannot be done through DNS, you should edit the /etc/hosts file so that it looks as follows on both systems:

vi /etc/hosts

127.0.0.1               localhost.localdomain localhost
192.168.0.100           server1.example.com server1
192.168.0.101           client1.example.com client1

(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 Setting Up The GlusterFS Server

server1.example.com:

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

urpmi glusterfs-server

The command

glusterfs –version

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

[root@server1 administrator]# glusterfs –version
glusterfs 2.0.6 built on Sep 20 2009 06:40:50
Repository revision: v2.0.6
Copyright (c) 2006-2009 Z RESEARCH Inc. <http://www.zresearch.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.
[root@server1 administrator]#

Next we create a few directories:

mkdir /data/
mkdir /data/export
mkdir /data/export-ns

Now we create the GlusterFS server configuration file /etc/glusterfs/glusterfsd.vol which defines which directory will be exported (/data/export) and what client is allowed to connect (192.168.0.101 = client1.example.com):

vi /etc/glusterfs/glusterfsd.vol

volume posix
  type storage/posix
  option directory /data/export
end-volume

volume locks
  type features/locks
  option mandatory-locks on
  subvolumes posix
end-volume

volume brick
  type performance/io-threads
  option thread-count 8
  subvolumes locks
end-volume

volume server
  type protocol/server
  option transport-type tcp
  option auth.addr.brick.allow 192.168.0.101 # Edit and add list of allowed clients comma separated IP addrs(names) here
  subvolumes brick
end-volume

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. 192.168.0.101,192.168.0.102).

Afterwards we restart the GlusterFS server:

/etc/init.d/glusterfsd restart

3 Setting Up The GlusterFS Client

client1.example.com:

On the client, we can install the GlusterFS client as follows:

urpmi glusterfs-client glusterfs-server

Then we create the following directory:

mkdir /mnt/glusterfs

Next we create the file /etc/glusterfs/glusterfs.vol:

vi /etc/glusterfs/glusterfs.vol

volume remote
  type protocol/client
  option transport-type tcp
  option remote-host server1.example.com # can be IP or hostname
  option remote-subvolume brick
end-volume

volume writebehind
  type performance/write-behind
  option window-size 4MB
  subvolumes remote
end-volume

volume cache
  type performance/io-cache
  option cache-size 512MB
  subvolumes writebehind
end-volume

Make sure you use the correct server hostname or IP address in the option remote-host line!

That’s it! Now we can mount the GlusterFS filesystem to /mnt/glusterfs with one of the following two commands:

glusterfs -f /etc/glusterfs/glusterfs.vol /mnt/glusterfs

or

mount -t glusterfs /etc/glusterfs/glusterfs.vol /mnt/glusterfs

You should now see the new share in the outputs of…

mount

[root@client1 administrator]# mount
/dev/sda1 on / type ext4 (rw,relatime)
none on /proc type proc (rw)
/dev/sda6 on /home type ext4 (rw,relatime)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
/etc/glusterfs/glusterfs.vol on /mnt/glusterfs type fuse.glusterfs (rw,allow_other,default_permissions,max_read=131072)
[root@client1 administrator]#

… and…

df -h

[root@client1 administrator]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1              12G  1.5G  9.8G  13% /
/dev/sda6              16G  172M   16G   2% /home
/etc/glusterfs/glusterfs.vol
29G  1.7G   26G   6% /mnt/glusterfs
[root@client1 administrator]#

Instead of mounting the GlusterFS share manually on the client, you could modify /etc/fstab so that the share gets mounted automatically when the client boots.

Open /etc/fstab and append the following line:

vi /etc/fstab

[...]
/etc/glusterfs/glusterfs.vol  /mnt/glusterfs  glusterfs  defaults  0  0

To test if your modified /etc/fstab is working, reboot the client:

reboot

After the reboot, you should find the share in the outputs of…

df -h

… and…

mount

 

  • GlusterFS: http://www.gluster.org/
  • Mandriva: http://www.mandriva.com/

Comments

comments