All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Bryan Schumaker <bjschuma@netapp.com>, linux-nfs@vger.kernel.org
Subject: Re: nfs4 mounts failing with 3.6.0-rc1
Date: Tue, 7 Aug 2012 13:09:32 -0400	[thread overview]
Message-ID: <20120807130932.79625d7e@tlielax.poochiereds.net> (raw)
In-Reply-To: <20120804190104.GA2135@fieldses.org>

On Sat, 4 Aug 2012 15:01:04 -0400
"J. Bruce Fields" <bfields@fieldses.org> wrote:

> On Fri, Aug 03, 2012 at 10:00:39PM -0400, Jeff Layton wrote:
> > On Fri, 3 Aug 2012 20:08:19 -0400
> > "J. Bruce Fields" <bfields@fieldses.org> wrote:
> > 
> > > I'm getting
> > > 
> > > 	# mount -tnfs -onfsvers=4 pip1:/exports /mnt/
> > > 
> > > (OK, admittedly that's with 3.6.0-rc1 + a few experimental patches, but
> > > I doubt they're related.)
> > > 
> > > Also:
> > > 
> > > 	[root@pip2 ~]# modprobe nfs4
> > > 	[root@pip2 ~]# lsmod|grep nfs4
> > > 	[root@pip2 ~]# 
> > > 
> > > --b.
> > 
> > I hit the same problem...
> > 
> > Try removing /usr/lib/modprobe.d/nfs.conf (assuming you're running
> > Fedora).
> 
> Oog, right.
> 
> But, without testing--won't that make v4 mounts fail on older kernels?

Actually, now that I look, this does not seem to break on older kernels
as long as you use a syntax like:

    # mount -t nfs server:/export /mnt/point -o vers=4

...if, however you use a syntax like:

    # mount -t nfs4 server:/export /mnt/point

...then it fails without the above file in place. I guess the question
we have to answer is: Do we want to continue to support the "-t nfs4"
mount syntax?

-- 
Jeff Layton <jlayton@redhat.com>

  parent reply	other threads:[~2012-08-07 17:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-04  0:08 nfs4 mounts failing with 3.6.0-rc1 J. Bruce Fields
2012-08-04  2:00 ` Jeff Layton
2012-08-04 19:01   ` J. Bruce Fields
2012-08-04 20:02     ` Jeff Layton
2012-08-07 17:09     ` Jeff Layton [this message]
2012-08-07 19:42       ` J. Bruce Fields
2012-08-07 19:44         ` Bryan Schumaker
2012-08-07 19:57           ` J. Bruce Fields
2012-08-07 20:10             ` Bryan Schumaker
2012-08-07 20:25               ` J. Bruce Fields
2012-08-07 21:23                 ` Myklebust, Trond
2012-08-07 22:26                   ` Jeff Layton
2012-08-07 22:36                     ` Myklebust, Trond
2012-08-08 11:48                       ` Jeff Layton
2012-08-08 14:42                   ` Bryan Schumaker
2012-08-08 15:08                     ` Myklebust, Trond
2012-08-08 15:15                       ` Bryan Schumaker
2012-08-08 15:24                         ` Myklebust, Trond
2012-08-08 15:25                           ` Bryan Schumaker

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=20120807130932.79625d7e@tlielax.poochiereds.net \
    --to=jlayton@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=bjschuma@netapp.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.