Red Hat Bugzilla – Bug 1004796
glusterd.service (systemd), ensure glusterd starts before any local gluster or nfs mounts
Last modified: 2014-04-17 09:14:20 EDT
+++ This bug was initially created as a clone of Bug #1004795 +++
Description of problem: Users who mount gluster volumes locally, i.e. on the brick server, from /etc/fstab usually have the mount fail because glusterd isn't started early enough and thus hasn't started the glusterfsds.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Also need to use _netdev as an option for glusterfs native mounts. systemd recognizes nfs and implicitly applies _netdev semantics.
REVIEW: http://review.gluster.org/5824 (glusterd.service (systemd), ensure glusterd starts early, (backport BZ 1004795)) posted (#1) for review on release-3.4 by Kaleb KEITHLEY (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/5824 committed in release-3.4 by Anand Avati (email@example.com)
Author: Kaleb S. KEITHLEY <firstname.lastname@example.org>
Date: Thu Sep 5 10:30:25 2013 -0400
glusterd.service (systemd), ensure glusterd starts early, (backport BZ 1004795)
Try (emphasis on the try) to ensure that glusterd starts, and in turn
starts glusterfsd before init attempt to mount any gluster (or gluster
NFS) volumes in /etc/fstab.
N.B. Joe Julian says this doesn't fix the problem for him, although it
worked for me in kvm. Lennart Poettering says it should, and we should
file a BZ against systemd if it doesn't. See
Signed-off-by: Kaleb S. KEITHLEY <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Anand Avati <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.4.3, please reopen this bug report.
glusterfs-3.4.3 has been announced on the Gluster Developers mailinglist , packages for several distributions should already be or become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.
The fix for this bug likely to be included in all future GlusterFS releases i.e. release > 3.4.3. In the same line the recent release i.e. glusterfs-3.5.0  likely to have the fix. You can verify this by reading the comments in this bug report and checking for comments mentioning "committed in release-3.5".