Created attachment 592
I asked about this issue on Fedora/CentOS platforms in IRC and it seems to only affect Ubuntu, and not the other distributions that use upstart. This is most likely due to the fact that Ubuntu uses the mountall program to handle fstab mounts while other distributions do it some other way.
see also http://review.gluster.com/126
Ubuntu uses upstart instead of init to bootstrap the system. As a result, glusterfs mounts in fstab are tried before the glusterd service is running. In the case where the client is also a server and the volume is mounted from localhost, the mount fails at boot time. An upstart job for glusterd is needed to correct this.
I have attached my upstart job which I have tested on Ubuntu 10.10 Maverick. The file should be placed in /etc/init/glusterd.conf, and replaces the old initscript in /etc/init.d/glusterd which can be removed.
This affects all versions of glusterfs on the ubuntu platform. It may also affect other platforms that use upstart like Fedora (9+) and RHEL/CentOS (6+), though I have not tried them.
CHANGE: http://review.gluster.com/126 (Mounting from localhost in fstab fails at boot on ubuntu when glusterd is started by debian initscript.) merged in master by Anand Avati (firstname.lastname@example.org)
I have been working with Ubuntu devs to get upstart jobs for glusterd in the Ubuntu package for glusterfs-server. In the process they helped me fix up the upstart job configuration. I'm committing the new upstart jobs now.
CHANGE: http://review.gluster.com/2727 (Updated the Ubuntu upstart jobs for glusterd in extras/Ubuntu.) merged in master by Anand Avati (email@example.com)
I do not see any of these changes as part 3.3.0, will be testing again in next release.