All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: mount.nfs: protocol fallback when server doesn't support TCP
Date: Tue, 7 Sep 2010 10:02:07 +1000	[thread overview]
Message-ID: <20100907100207.5119d61c@notabene> (raw)
In-Reply-To: <4B6431AA-0FFD-4FE9-9DF4-4AF7D2B2AD20@oracle.com>

On Tue, 31 Aug 2010 16:29:59 -0400
Chuck Lever <chuck.lever@oracle.com> wrote:

> 
> On Aug 30, 2010, at 9:00 PM, Neil Brown wrote:
> 
> > Two observations I've made while exploring which are only tangential to the
> > current issue:
> > 
> > 1/ if I give an invalid proto name
> >          mount -o proto=fred .....
> >    the mount command fails (as it should) but gives no error message.
> 
> I was not able to reproduce this.  I get an appropriate error message from mount.nfs when built either with TI-RPC or without.  I'm using the latest upstream nfs-utils + my mountd patches.
> 

Ahh yes, fixed by

commit 9ac7a15017b876d4d8d3a4502ebaf954f36f7f54
Author: Steve Dickson <steved@redhat.com>
Date:   Thu Jun 3 08:53:22 2010 -0400

    mount.nfs: silently fails when the network protocol is not found
    
    mount.nfs should display some type of error diagnostics when
    the network protocol can not be determined.
    
    Signed-off-by: Steve Dickson <steved@redhat.com>


Thanks,
NeilBrown

      reply	other threads:[~2010-09-07  0:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-26  2:06 mount.nfs: protocol fallback when server doesn't support TCP Neil Brown
2010-08-26 14:51 ` Chuck Lever
2010-08-26 15:27   ` Jim Rees
2010-08-26 16:09     ` Chuck Lever
2010-08-30  0:30   ` Neil Brown
2010-08-30 19:29     ` Chuck Lever
2010-08-31  1:00       ` Neil Brown
2010-08-31 16:38         ` Chuck Lever
2010-09-07  1:32           ` Neil Brown
2010-09-07 17:37             ` Chuck Lever
2010-09-08  2:35               ` Neil Brown
2010-09-08 18:52                 ` Chuck Lever
2010-08-31 20:29         ` Chuck Lever
2010-09-07  0:02           ` Neil Brown [this message]

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=20100907100207.5119d61c@notabene \
    --to=neilb@suse.de \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    /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.