On 08.06.2012 22:39, Jamie Heilman wrote: > Michael Tokarev wrote: [] >> On the other hand, -vers=4 does NOT work, because automount only checks >> for -fstype and -port, but not -vers. This is a defect in autofs, but >> it is a small defect. I think it can be made to work with -vers=4 too >> the same way it works with -fstype=nfs4, that should be easy. > > Yeah, I'm testing a patch for this atm...
That's a trivial patch actually, adding strstr(options, "vers=4") to the same place where port= or fstype=nfs4 is checked. >> Meanwhile, the trivial workaround is to specify -fstype=nfs4 and/or >> -port, instead of using -vers. Not obvious, that's for sure, but it >> works and it is simple. > > There's a lot of documentation problems, I'm working up patches for > those too. As it turns out, you shouldn't have to specify the port > for nfs4... see port=n in nfs(5) under the "Options for NFS version 4 > only" section. That's okay. For mount.nfs, port= isn't needed for nfsv4, it tries to use 2049 port directly first. But it doesn't hurt to specify port=2049 either, this does not change the behavour of mount.nfs, but allows to trick automount to not do portmapper calls. > Figuring out a way to probe NFSv4 servers that doesn't involve the rpc > ping is, IMO, what needs to happen. Maybe for single hosts, it's > less important, but the probing and weighting that automount does is > necessary for replicated exports. Yes. >> Either using -port OR -fstype=nfv4 should work. Please verify if >> it works for you. Specifying -port= is a bit ugly to my taste, but >> -fstype=nfs4 is as good as -vers=4. > > To make matters even more fun, there's a bug in the 3.5-rc kernels at > the moment that prevents -fstype=nfs4 from working all by itself... > but it's in the process of being worked out thankfully. Well. That's a bug which will be fixed. Meanwhile, nfs(5) says that fstype=nfs4 is deprecated and nfs should be used instead. So the workaround in automount - to use -fstype=nfs4 - is wrong, but it should work still (give or take bugs which needs to be fixed). Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
