old nfs client, new nfs host, incorrect mount option?

[Tom H]

On Fri, Apr 10, 2015 at 8:18 PM, Rick Stevens <ricks at alldigital.com> wrote:
> On 04/10/2015 04:35 PM, Tom H wrote:
>> On Thu, Apr 9, 2015 at 9:15 AM, Tom Horsley <horsley1953 at gmail.com> wrote:
>>
>> You could use "nfs4" for all of your mounts from F11 to F21, until
>> it's removed, if ever.
>>
>> You can check which nfs versions are being used by an nfs server with
>> "cat /proc/fs/nfsd/versions" or "rpcinfo -s" or "rpcinfo -p".
>>
>> CentOS 7 defaults to nfsv4 but unless you've disabled nfsv3 or are
>> running a firewall and haven't set nfs up to share through it, nfsv3
>> mounts should work. Try "mount -v -t nfs ..." on your F11 box and you
>> might get a more verbose error message (if you're lucky!).
>
> I think just specifying "-t nfs" should make the client negotiate with
> the server and try to get you the latest that the server provides.
> You'd use the "nfsvers=" stuff to force it one way or the other. You'd
> use "proto=" to force UDP or TCP (UDP default in V3, TCP in V4).

But the other Tom H said that "-t nfs" was failing when mounting a
CentOS 7 share from an F11 system...