Creating An NFS-Like Standalone Storage Server With GlusterFS On Fedora 12 - Page 2
3 Setting Up The GlusterFS Client
There's a GlusterFS client rpm package for Fedora 12, but the problem with it is that you will get errors like df: `/mnt/glusterfs': Software caused connection abort or df: `/mnt/glusterfs': Transport endpoint is not connected when you try to access the GlusterFS share. That's why we build the GlusterFS client from the sources to avoid these problems.
Before we build the GlusterFS client, we install its prerequisites:
yum groupinstall 'Development Tools'
yum groupinstall 'Development Libraries'
yum install libibverbs-devel fuse-devel
Then we download the GlusterFS 2.0.9 sources (please note that this is the same version that is installed on the server!) and build GlusterFS as follows:
At the end of the ./configure command, you should see something like this:
make && make install
Check the GlusterFS version afterwards (should be 2.0.9):
[root@client1 glusterfs-2.0.9]# glusterfs --version
Then we create the following two directories:
Next we create the file /etc/glusterfs/glusterfs.vol:
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
mount -t glusterfs /etc/glusterfs/glusterfs.vol /mnt/glusterfs
You should now see the new share in the outputs of...
[root@client1 glusterfs-2.0.9]# mount
[root@client1 glusterfs-2.0.9]# df -h
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:
To test if your modified /etc/fstab is working, reboot the client:
After the reboot, you should find the share in the outputs of...