The addr= bit was added because I had a NIC with multiple IP addrs and thought that that might be confusing it as the NFS docs state that the "server IP resolution logic" is not entirely correct.
There are however some servers that have this problem and some that don't.
OK:
Intel(R) Xeon(R) CPU X5680 @ 3.33GHz
Not OK:
Intel(R) Xeon(R) CPU E5405 @ 2.00GHz
AMD Opteron(tm) Processor 280
Intel(R) Xeon(TM) CPU 3.00GHz
They are all using the same mount args as provided by LDAP autofs.
It may be just the use case that has prevented it from happening on that one server.
I've tried all of the 10.10 ppa kernel backports as they are made available. This has made no difference. Each one in turn.
I've also played with the mount lines. Here are some of the combinations I've tried:
rw,noatime, nfsvers= 3,udp,rsize= 32768,wsize= 32768,actimeo= 3,sloppy, addr=135. 149.74. 51
udp -> tcp
no nfsvers=3
no actimeo
no noatime
The addr= bit was added because I had a NIC with multiple IP addrs and thought that that might be confusing it as the NFS docs state that the "server IP resolution logic" is not entirely correct.
There are however some servers that have this problem and some that don't.
OK:
Intel(R) Xeon(R) CPU X5680 @ 3.33GHz
Not OK:
Intel(R) Xeon(R) CPU E5405 @ 2.00GHz
AMD Opteron(tm) Processor 280
Intel(R) Xeon(TM) CPU 3.00GHz
They are all using the same mount args as provided by LDAP autofs.
It may be just the use case that has prevented it from happening on that one server.