or maybe something like fetch-attempts=5
vm1:/v /var/volumes/vol-1 glusterfs defaults,_netdev,negative-timeout=10,attribute-timeout=30,fopen-keep-cache,direct-io-mode=enable,fetch-attempts=5 0 0
On Thu, Jul 26, 2018 at 6:36 AM, Anoop C S <anoopcs@xxxxxxxxxxxxx> wrote:
On Thu, 2018-07-26 at 12:23 +0200, Stefan Kania wrote:
> Hello,
>
> I have the following problem:
> If I reboot a node in a gluster-cluster on a Debian- or Ubuntu-System
> the fuse-mount is not working if I just put the mount-options into the
> /etc/fstab. For this reason I wrote a systemd-script as followed:
> -----------------
> [Unit]
> Description = Data dir
> After=network.target glusterfs-server.service
> Required=network-online.target
> [Mount]
> What=c1:/gv1
> Where=/glusterfs
> Type=glusterfs
> Options=defaults,acl
> [Install]
> WantedBy=multi-user.target
> -----------------
> Somtimes the the volume will be mounted and sometime not. I can't figure
> out why it's sometime not mounting the volume. If I execute the script
> after a reboot the volume is mounting, so the script is working only the
> conditions during the boot-process are the problem (I think). Can
> someone give me a hint where to change things in my script?
Instead of this custom script, does it help if you put the following option to /etc/fstab?
x-systemd.requires=<service name>
See http://man7.org/linux/man-pages/man5/systemd.mount.5. for more details.html#FSTAB
> It dosn't matter which gluster-version or which OS-Version I use it's
> always the same.
>
> Stefan
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users@xxxxxxxxxxx
> https://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
