On Fri, 27 Apr 2012 15:02:07 +0000 "Myklebust, Trond" <Trond.Myklebust@xxxxxxxxxx> 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@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
