<div dir="ltr">I'll have to understand the effects of lock=false better. From gluster's standpoint though, this appears to be a limitation/bug. Autofs continues to work fine if it is started after gluster's nfs server is started. i.e. It can adapt to gluster's nfs server, but not the other way around. </div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 19, 2015 at 1:07 PM, Jason Brooks <span dir="ltr"><<a href="mailto:jbrooks@redhat.com" target="_blank">jbrooks@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
----- Original Message -----<br>
> From: "Prasun Gera" <<a href="mailto:prasun.gera@gmail.com">prasun.gera@gmail.com</a>><br>
</span><span class="">> To: "Jason Brooks" <<a href="mailto:jbrooks@redhat.com">jbrooks@redhat.com</a>><br>
> Cc: <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> Sent: Monday, May 18, 2015 3:26:02 PM<br>
> Subject: Re: [Gluster-users] Can a gluster server be an NFS client ?<br>
><br>
> Thanks. Can you tell me what this achieves, and what the side-effects, if<br>
> any, are ? Btw, the NFS mounts on the gluster server are unrelated to what<br>
> the gluster server itself is exporting. They are regular nfs mounts from a<br>
> different NFS server.<br>
<br>
</span>Your nfs client and the gluster nfs server are both vying for portmap,<br>
turning off locking for the client resolves this. The side effects will<br>
depend on your environment -- in my converged ovirt+gluster setup,<br>
it isn't causing an issue, but I'm looking forward to dropping this<br>
workaround when ovirt gets support for hosting its engine vm from<br>
native gluster.<br>
<br>
For you, this may or may not be a workable workaround.<br>
<span class="HOEnZb"><font color="#888888"><br>
Jason<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
> On Mon, May 18, 2015 at 5:35 PM, Jason Brooks <<a href="mailto:jbrooks@redhat.com">jbrooks@redhat.com</a>> wrote:<br>
><br>
> ><br>
> ><br>
> > ----- Original Message -----<br>
> > > From: "Prasun Gera" <<a href="mailto:prasun.gera@gmail.com">prasun.gera@gmail.com</a>><br>
> > > To: <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> > > Sent: Monday, May 18, 2015 1:47:32 PM<br>
> > > Subject: [Gluster-users] Can a gluster server be an NFS client ?<br>
> > ><br>
> > > I am seeing some erratic behavior w.r.t. the NFS service on the gluster<br>
> > > servers (RHS 3.0). The nfs service fails to start occasionally and<br>
> > randomly<br>
> > > with<br>
> > ><br>
> > > Could not register with portmap 100021 4 38468<br>
> > > Program NLM4 registration failed<br>
> > ><br>
> ><br>
> > I've encountered this before -- I had to disable file locking,<br>
> > adding Lock=False to /etc/nfsmount.conf<br>
> ><br>
> > > This appears to be related to<br>
> > > <a href="http://www.gluster.org/pipermail/gluster-users/2014-October/019215.html" target="_blank">http://www.gluster.org/pipermail/gluster-users/2014-October/019215.html</a><br>
> > ,<br>
> > > although I'm not sure what the resolution is.<br>
> > ><br>
> > > The gluster servers use autofs to mount user home directories and other<br>
> > > sundry directories. I could verify that stopping autofs and then starting<br>
> > > the gluster volume seems to solve the problem. Starting autofs after<br>
> > > gluster seems to work fine too. What's the right way to handle this ?<br>
> > ><br>
> > > _______________________________________________<br>
> > > Gluster-users mailing list<br>
> > > <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> > > <a href="http://www.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
> ><br>
><br>
</div></div></blockquote></div><br></div>