Re: Status of mount.nfs

[Trond Myklebust <trond.myklebust@fys.uio.no>]

On Tue, 2007-07-24 at 16:46 -0400, Chuck Lever wrote:

> The TCP case fails because mount.nfs is using the portmapper even though 
> the user has specified the ports on the command line.  Could that be the 
> root cause of the failure?

If the user specifies a port, then there is no real good reason to use
the portmapper:

      * For the case of the mount protocol, we should just try an RPC
        call and then look at the returned RPC error values to figure
        out which versions of the protocol are supported if it fails (or
        alternatively, fall back to UDP if the TCP connection fails).
      * If the mount call has succeeded and we have a port for the NFS
        server, we should probably just try the mount call for a
        sufficiently recent kernel, then look at the returned error
        codes. For older kernels (pre 2.6.13?) which don't return decent
        error values, then ping first in userland and look at the RPC
        return values. Retry with UDP if TCP doesn't work...

Trond


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs