Comment 12 for bug 1103047

Ok so the situation was as following.

In boot.log we have:

mounted event handled for /var/www
local 2/3 remote 1/1 virtual 9/10 swap 0/0
Mount failed. Please check the log file for more details.
mountall: mount /var/www [337] terminated with status 1
Filesystem could not be mounted: /var/www

The thing is the log file mentionned, which I suppose to be the gluster log file, does not exist.
Multiple attempts (and this one I do not explain) permitted me to have one time in boot.log a message stating that /va/log/glusterfs/var-www.log did not exist.

Actually the folder exist, and permissions are fine as well.

The only thing is that actually my /var/log is a dedicated partition like often on servers.
I commented this out in fstab for a try, and managed to have the /va/log/glusterfs/var-www.log writtend at boot time.

[2013-03-21 21:55:45.968441] I [glusterfsd.c:1666:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.3.1
[2013-03-21 21:55:45.970384] E [common-utils.c:125:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Name or service not known)
[2013-03-21 21:55:45.970471] E [name.c:243:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution failed on host storage.domain.com
[2013-03-21 21:55:45.970503] E [glusterfsd-mgmt.c:1787:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed to connect with remote-host: Success
[2013-03-21 21:55:45.970523] I [glusterfsd-mgmt.c:1790:mgmt_rpc_notify] 0-glusterfsd-mgmt: 2 connect attempts left

The fstab line is:
storage.domain.com:web-g-www /var/www glusterfs defaults,_netdev,backupvolfile-server=172.18.2.130,fetch-attempts=1 0 0

I'm not sure where the "2 connect attempts left" is coming from as I indicated fetch-attempts=1 is the fstab.

Still we can see that DNS resolution is failing, may be indicating that the network is not really up when mountall is trying to mount glusterfs filesytems.

Setting fetch-attempts=3 in the fstab managed to have all filesystem properly mounted, including glusterfs.

So this tell us a few things:
- network does not seem to be up when mountall try to mount glustersfs filesystems (at least DNS is failing)
- there may be a missing dependency on having local fs up before trying to mount remote ones, because obviously the "log" file that could help in debugging this issue is not available for write when mountall (thus glusterfs) tries to write to it. (this is fixed by not separating /var/log but on a server may be dangerous then)

Hope this helps
--
Bruno