I would like to just suggest... I'm aware that some ppl migh want to start a long debate about this (which I will then just have to dodge)
If you really really want to deploy v4.x in an ubiquitous manner, scale it up/out a lot so to speak for some good reason you have thought trough really well.
Do it with NFS clients that can talk 4.1 (i.e. minorversion=1.) NFS clients which do not understand v4.1 but only 4.0, deny them any v4 access, this can be done by simply disabling v4.0 in the vservers configs, but keep 4.1 enabled. Just make those older NFS clients fall back to v3 and all will work, the users won't notice any difference and there's no real loss of anything that you will miss
(AUTH_GSS, aka RPCSEC_GSS, with sec=krb5{,i,p} is supported and works just fine with NFSv3 in ONTAP and in almost all if not all, wide-spread Linux distros as well as Oracle Solaris. Don't know about *BSD).
/M
On 2016-11-03 19:41, Steiner, Jeffrey wrote:
Just a thought - I ran into a similar problem once where what happened was I upgraded and ended up with a system enabled for 4.1 when previously only 4.0 was enabled. A few clients glitched because they detected the change and tried to connect with NFSv4.1. I had to explicitly force the mount to v4.0 only.