====== glusterfs ======

  * [[Filesystems]]
  * [[mkfs.xfs]]

  * uses NFS
  * very few dependencies
  * can run on top of any filesystem
  * automatic failover

Things I'm not sure about:

  * no-metadata server architecture
  * noted some performance slowdown with Samba
  * using any filesystem means that they're not taking advantage of some situations, or may be not using a large featureset; generally, it makes me think this is more of a hobby setup ("we can run anywhere!") than a production one ("use these for best practices")

==== Setup ====

  * [[http://gluster.readthedocs.org/en/latest/Quick-Start-Guide/Quickstart/|Quick Start Guide]]

Create an format a partition for the node:

<code>
mkfs.xfs -i size=512 /dev/sdb1
mount /dev/sdb1 /var/gluster
mkdir /var/gluster/brick
</code>

Add an entry to ''/etc/fstab'' for each server:

<code>
/dev/sdb1 /var/gluster/brick1 xfs noatime 0 0
</code>

Mount the drive, and start the glusterfs daemon:

<code>
mount -a
/etc/init.d/glusterd start
</code>

Have each server probe each other. On server1:

<code>
gluster peer probe server2
</code>

On server2:

<code>
gluster peer probe server1
</code>

On both servers, create the gluster volume directory:

<code>
mkdir /var/gluster/brick1/gv0
</code>

Then, from either server, create the gluster volume:

<code>
gluster volume create gv0 replica 2 server1:/var/gluster/gv0 server2:/var/gluster/gv0
gluster volume start gv0
</code>

You can check the status of the volume on either server:

<code>
gluster volume info
</code>

<code>
Volume Name: gv0
Type: Replicate
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: gluster1:/var/gluster/brick1/gv0
Brick2: gluster2:/var/gluster/brick1/gv0
</code>

If the status is not started, check the logs in ''/var/log/glusterfs'', usually in ''etc-glusterfs-glusterd.vol.log''.