[Gluster-users] One node goes offline, the other node can't see the replicated volume anymore

[Joe Julian]

On 07/15/2013 10:38 PM, Greg Scott wrote:
> Hmmm - I mount my firewall-scripts volume like this now in fstab:
>
> localhost:/firewall-scripts /firewall-scripts glusterfs defaults,_netdev 0 0
>
> But gluster volume info still looks like this on both nodes:
>
> [root at chicago-fw1 system]# gluster volume info
>
> Volume Name: firewall-scripts
> Type: Replicate
> Volume ID: 239b6401-e873-449d-a2d3-1eb2f65a1d4c
> Status: Started
> Number of Bricks: 1 x 2 = 2
> Transport-type: tcp
> Bricks:
> Brick1: 192.168.253.1:/gluster-fw1
> Brick2: 192.168.253.2:/gluster-fw2
> [root at chicago-fw1 system]#
>
> Seems to me, my Gluster volume would still have some dependency on networking, even though I mount it with localhost in fstab, right?
>
> In all our trial and error, the only thing that's worked so far is putting in that 30 second delay in my custom rc.local file.  So instead of fighting this, why not try my hand at a systemd service file named, say, glustermount.service.
>
> So here is the glustermout.service file I made.  It runs a script named /etc/rc.d/glustermount.sh pasted in below.
>
>
The only reason why not would be because it should be able to mount 
during the normal netfs mount process. I have an idea how to fix that 
properly. Your hack would certainly work though.