[Gluster-users] Some client problems with TCP-only NFS in Gluster 3.1

[Shehjar Tikoo]

Brent A Nelson wrote:
> Alas, that does not work on Solaris 2.6 or 7.  Solaris 7 was apparently 
> the first to support the WebNFS URL syntax, but it otherwise has the 
> same behavior as 2.6.  Both seem to be hardwired to look for the UDP 
> mountd port, even when told to use TCP.  On each, you can specify the 
> NFS port, but apparently not the mountd port (there's no mountport 
> option documented).

Yes, thats broken in Solaris. Without WebURL, if we specify proto=tcp, 
it defaults to using NFSv4. If we then try to override using vers=3 
option, as the man page says we can, it falls back to using UDP even 
when proto=tcp is given.

These versions will need UDP support in gluster nfs to work.

-Shehjar

> 
> Perhaps they got it right in Solaris 8 or greater, at least for WebNFS, 
> but I no longer have any newer Solaris with which to test...
> 
> Thanks,
> 
> Brent
> 
> On Fri, 22 Oct 2010, Craig Carl wrote:
> 
>> {Resending due to incomplete response]
>>
>> Brent,
>> Thanks for your feedback . To mount with a Solaris client use -
>> ` mount -o proto=tcp,vers=3 nfs://<SERVER-ADDR>:38467/<EXPORT> 
>> <MNT-POINT>`
>>
>> As to UDP access we want to force users to use TCP. Everything about 
>> Gluster is designed to be fast , as NFS over UDP approaches line speed 
>> it becomes increasingly inefficient, [1] we want to avoid that.
>>
>> I have updated our documentation to reflect the required tcp option 
>> and Solaris instructions.
>>
>> [1] http://nfs.sourceforge.net/#faq_b10
>>
>>
>> Thanks again,
>>
>> Craig
>>
>> -->
>> Craig Carl
>> Senior Systems Engineer
>> Gluster
>>
>>
>> From: "Brent A Nelson" <brent at phys.ufl.edu>
>> To: gluster-users at gluster.org
>> Sent: Thursday, October 21, 2010 8:18:02 AM
>> Subject: [Gluster-users] Some client problems with TCP-only NFS in 
>> Gluster 3.1
>>
>> I see that the built-in NFS support registers mountd in portmap only with
>> tcp and not udp. While this makes sense for a TCP-only NFS
>> implementation, it does cause problems for some clients:
>>
>> Ubuntu 10.04 and 7.04 mount just fine.
>>
>> Ubuntu 8.04 gives "requested NFS version or transport protocol is not
>> supported", unless you specify "-o mountproto=tcp" as a mount option, in
>> which case it works just fine.
>>
>> Solaris 2.6 & 7 both give "RPC: Program not registered". Solaris
>> apparently doesn't support the mountproto=tcp option, so there doesn't
>> seem to be any way for Solaris clients to mount.
>>
>> There may be other clients that assume mountd will be contactable via
>> udp, even though they (otherwise) happily support TCP NFS...
>>
>> Thanks,
>>
>> Brent
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users