public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: nfsv4@linux-nfs.org
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [RFC] [PATCH] mount.nfs: Retry v4 mounts with v3 on ENOENT errors
Date: Tue, 03 Nov 2009 08:16:10 -0500	[thread overview]
Message-ID: <4AF02D1A.3060500@RedHat.com> (raw)
In-Reply-To: <4ADDCB52.2050906@RedHat.com>

On 10/20/2009 10:38 AM, Steve Dickson wrote:
> I'm trying to convince myself this is a good idea... 
> 
> It would definitely help with the v3 to v4 transition
> in the Linux community, but at the end of the day, 
> Linux servers that numerous compared to other types 
> of server so its not clear this will not cause other 
> problems...
> 
> Comments? Suggestions?
> 
> steved.
> 
> Author: Steve Dickson <steved@redhat.com>
> Date:   Tue Oct 20 10:25:34 EDT 2009
> 
>     Retry v4 mounts with a v3 mount when the version
>     is not explicitly specified and the mount fails 
>     with ENOENT. The will help deal with Linux servers
>     that do not automatically export a pseudo root
> 
>     Signed-off-by: Steve Dickson <steved@redhat.com>
> 
> diff -up nfs-utils-1.2.0/utils/mount/stropts.c.orig nfs-utils-1.2.0/utils/mount/stropts.c
> --- nfs-utils-1.2.0/utils/mount/stropts.c.orig	2009-10-20 10:11:03.000000000 -0400
> +++ nfs-utils-1.2.0/utils/mount/stropts.c	2009-10-20 10:24:41.000000000 -0400
> @@ -613,8 +613,15 @@ static int nfs_try_mount(struct nfsmount
>  		if (linux_version_code() > MAKE_VERSION(2, 6, 31)) {
>  			errno = 0;
>  			result = nfs_try_mount_v4(mi);
> -			if (errno != EPROTONOSUPPORT)
> -				break;
> +			if (errno != EPROTONOSUPPORT) {
> +				/* 
> +				 * To deal with legacy Linux servers that don't
> +				 * automatically export a pseudo root, retry
> +				 * ENOENT errors using version 3
> +				 */
> +				if (errno != ENOENT)
> +					break;
> +			}
>  		}
>  	case 2:
>  	case 3:
I am going to go ahead an commit this and then cut a release. I 
was waiting to include the server side dynamic pseudo root support, 
but it appears that will not happen in a timely matter... 

After this release, I will actively start catching up on the backlog
of purposed patches... Thank you for your patiences....  

steved.

           reply	other threads:[~2009-11-03 13:16 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <4ADDCB52.2050906@RedHat.com>]

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=4AF02D1A.3060500@RedHat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox