[Gluster-users] NFS mount

[Prasun Gera]

Your gluster node cannot be an nfs client either. If you are using autofs
or even fstab for mounting other NFS shares, it will stop gluster nfs from
starting due to the NLM conflict. I have found that starting autofs after
glusterd seems to work. It has also been suggested to try adding Lock=False
to /etc/nfsmount.conf, although I don't know if that is safe. Try these
steps: 1) Unmount all nfs shares on the gluster node 2) stop autofs if it's
running 3) Delete the rpc registration by rpcinfo -d <program>  <version>
as suggested earlier in the thread 4) Restart glusterd 5) You can try
starting autofs now or calling mount -a to mount your fstab shares. I have
found them to work.

On Thu, Aug 20, 2015 at 4:31 AM, shacky <shacky83 at gmail.com> wrote:

> > One way is to have your storage node separate and mount them where you
> are doing
> > the compute.
>
> I know it's the better solution, but I cannot do that unfortunately
> because I don't have any dedicated nodes available.
>
> > The other way is to mount Gluster NFS with "-o nolock" option. AFAIK,
> with nolock
> > the conflict from NLM will go away. But I need someone from NFS team to
> confirm this.
>
> I will try, but now my problem is that the Gluster NFS server is not
> starting at all...
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150820/6fa450fe/attachment.html>