Linux NFS development
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: Status of mount.nfs
Date: Tue, 24 Jul 2007 17:18:49 -0400	[thread overview]
Message-ID: <46A66CB9.9050805@oracle.com> (raw)
In-Reply-To: <1185311449.6586.69.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]



Trond Myklebust wrote:
> 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:

Exactly.

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

I'm wondering how much of this is already implemented in mount.nfs, but 
is just broken.  I'm reviewing the code now.

I cleaned this up a little with recent patches so it should be easier to 
figure out what's going wrong.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 259 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 315 bytes --]

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

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-07-24 21:20 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 [this message]
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
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=46A66CB9.9050805@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox