From: Jeff Layton <jlayton@redhat.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Josh Boyer <jwboyer@redhat.com>, Jim Rees <rees@umich.edu>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] NFSv4: Add modalias for "nfs4"
Date: Fri, 27 Apr 2012 11:27:09 -0400 [thread overview]
Message-ID: <20120427112709.08c99ec3@corrin.poochiereds.net> (raw)
In-Reply-To: <1335538927.3910.3.camel@lade.trondhjem.org>
On Fri, 27 Apr 2012 15:02:07 +0000
"Myklebust, Trond" <Trond.Myklebust@netapp.com> wrote:
> On Fri, 2012-04-27 at 10:53 -0400, Josh Boyer wrote:
> > On Fri, Apr 27, 2012 at 02:50:28PM +0000, Myklebust, Trond wrote:
> > > On Fri, 2012-04-27 at 10:48 -0400, Josh Boyer wrote:
> > > > On Fri, Apr 27, 2012 at 10:19:18AM -0400, Jim Rees wrote:
> > > > > Josh Boyer wrote:
> > > > >
> > > > > When NFSv4 is configured, the support goes into the nfs.ko module.
> > > > > However, nfs-utils seems to pass "nfs4" as the fileststem type for
> > > > > NFSv4 mounts.
> > > > >
> > > > > Weren't we going to change that to nfs and use nfsvers to select nfs4?
> > > >
> > > > I have, approximately, no idea. At least the version of nfs-utils found
> > > > in Fedora 17 and rawhide, it's still using "nfs4". I believe that is
> > > > nfs-utils-1.2.6-rc6 based.
> > >
> > > nfs4 is still _supported_ in Fedora 17, rawhide and upstream as a legacy
> > > feature, but the recommended practice should be to mount -t nfs -overs=4
> > > (or -overs=4.1).
> >
> > OK. So either this patch needs to go in, or something needs to add:
> >
> > alias nfs4 nfs
> >
> > to a conf file so modprobe picks it up. I figured the kernel could add
> > the alias itself. Is there a reason not to?
>
> Yes. This is a legacy feature that we want to encourage people to move
> their systems off...
>
Ahh ok...I guess I didn't get that memo. In that case, is there a plan
to deprecate the nfs4 fstype altogether?
Otherwise, you're going to end up with inconsistent behavior with "-t
nfs4", depending on whether nfs.ko is already plugged in at the time or
not.
--
Jeff Layton <jlayton@redhat.com>
prev parent reply other threads:[~2012-04-27 15:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 13:10 [PATCH] NFSv4: Add modalias for "nfs4" Josh Boyer
2012-04-27 13:30 ` Jeff Layton
2012-04-27 14:19 ` Jim Rees
2012-04-27 14:48 ` Josh Boyer
2012-04-27 14:50 ` Myklebust, Trond
2012-04-27 14:53 ` Josh Boyer
2012-04-27 15:02 ` Myklebust, Trond
2012-04-27 15:14 ` Josh Boyer
2012-04-27 15:21 ` Myklebust, Trond
2012-04-27 15:41 ` Josh Boyer
2012-04-27 15:27 ` Jeff Layton [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=20120427112709.08c99ec3@corrin.poochiereds.net \
--to=jlayton@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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