All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: chuck.lever@oracle.com
Cc: nfs@lists.sourceforge.net
Subject: Re: Status of mount.nfs
Date: Thu, 26 Jul 2007 08:47:09 -0400	[thread overview]
Message-ID: <46A897CD.50201@RedHat.com> (raw)
In-Reply-To: <46A7A5F8.4040204@oracle.com>



Chuck Lever wrote:
> 
> I'm looking at probe_nfsport() and probe_mntport() and I see that the 
> portmapper call is avoided iff the protocol version, transport protocol, 
> and the port number are all specified in advance.
> 
> So if you specify:
> 
>    -o mountport=650,port=2049
> 
> mount will still contact the server's portmapper to determine which 
> transport protocols are available (and this breaks through a firewall 
> that doesn't pass portmapper requests).  Only if you specify:
> 
>    -o tcp,mountport=650,port=2049
> 
> or
> 
>    -o udp,mountport=650,port=2049
> 
> then the portmapper calls are avoided entirely.  For some reason 
> probe_bothports() sets the default NFS version to 3 but does not set a 
> default transport protocol.
The protocol is set by probe_port().

> 
> The transport protocols are probed differently for NFS and MNT: for MNT, 
> UDP is probed first then TCP; for NFS, the opposite is true.  The mount 
> command is supposed to try both transport protocol types both for NFS 
> and MNT, but it appears that it is failing to try the other type if the 
> first fails... I see this is also problematic for umount.nfs.
The I idea here was to using UDP to probing for both rpc.mountd and the
NFS server so as not to put (tcp) ports in TIMEWAIT, basically making
them unavailable for the actual mount. The allowed many more tcp
mounts to happen during autofs mount storms.

Note: if the protocol was explicitly specified (i.e. proto=tcp) only
that protocol was used during the probing and mounting. I have
been asked to change that as well. Meaning if when proto=tcp is
specified, they still want the udp probing to occur.

steved.



-------------------------------------------------------------------------
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

  reply	other threads:[~2007-07-26 12:47 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08 19:16 Status of mount.nfs Steinar H. Gunderson
2007-07-08 23:16 ` Chuck Lever
2007-07-09  3:17 ` Neil Brown
2007-07-09  9:55   ` Steinar H. Gunderson
2007-07-09 16:45     ` Chuck Lever
2007-07-10  0:08       ` Neil Brown
2007-07-15  8:31   ` Steinar H. Gunderson
2007-07-16  1:13     ` Neil Brown
2007-07-16  9:20       ` Steinar H. Gunderson
2007-07-16 10:15         ` Neil Brown
2007-07-22 19:17           ` Steinar H. Gunderson
2007-07-22 21:58             ` Trond Myklebust
2007-07-22 22:04               ` Steinar H. Gunderson
2007-07-24 17:51                 ` Trond Myklebust
     [not found]             ` <46A52816.6050500@oracle.com>
2007-07-24 17:24               ` Steinar H. Gunderson
2007-07-24 17:50                 ` Trond Myklebust
2007-07-24 17:55                   ` Steinar H. Gunderson
2007-07-24 20:46                 ` Chuck Lever
2007-07-24 21:10                   ` Trond Myklebust
2007-07-24 21:18                     ` Chuck Lever
2007-07-25  2:08                 ` rpcbind behavior on Fedora 7 Chuck Lever
2007-07-25 19:35                 ` Status of mount.nfs Chuck Lever
2007-07-26 12:47                   ` Steve Dickson [this message]
2007-07-27  3:02                     ` Chuck Lever
2007-07-27 15:00                       ` Steve Dickson
2007-07-27 15:56                         ` Trond Myklebust
2007-07-27 16:16                           ` Steve Dickson
2007-07-27 16:27                             ` Trond Myklebust
2007-07-27 17:07                               ` Steve Dickson
2007-07-27 17:13                                 ` Trond Myklebust
2007-07-27 21:38                                   ` Chuck Lever
2007-07-28 12:51                                   ` Steve Dickson
2007-07-31 18:30                                     ` Trond Myklebust
2007-07-31 21:28                                       ` Chuck Lever
2007-08-01 10:58                                         ` Steve Dickson
2007-08-01 20:02                                           ` Chuck Lever
2007-08-01 21:12                                             ` Steve Dickson
2007-08-02 16:20                                               ` Chuck Lever
2007-08-02 18:42                                                 ` Trond Myklebust
2007-08-02 21:43                                                   ` Chuck Lever
2007-08-03 13:02                                                     ` Trond Myklebust
2007-08-02 20:46                                                 ` Steve Dickson
2007-07-27 19:37                         ` Chuck Lever
2007-07-28 13:20                           ` Steve Dickson
2007-07-28 21:00                             ` Chuck Lever
2007-07-29 19:24                               ` Steve Dickson
2007-07-30  4:14                                 ` Chuck Lever
2007-07-24 23:41     ` Steinar H. Gunderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46A897CD.50201@RedHat.com \
    --to=steved@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.