On Sun, 11 May 2008 13:43:49 +0100, Chris Ridd wrote:
> On 2008-05-11 13:32:32 +0100, Dave Uhring said:
>> On Sun, 11 May 2008 10:44:26 +0100, Chris Ridd wrote:
>>
>>> Is the Solaris NFSv4 client doing something wrong, or the NFSv4 server
>>> doing something wrong? It is a pity to have to downgrade to v3...
>>
>> The Solaris client *should* adapt to the capability of the server without
>> a kluge like that. It does not.
>
> I suppose there are a couple of things to ask then: a) why isn't NFSv4
> working, and b) as it isn't, why isn't the downgrade to NFSv3 working?

I don't know how an NFSv4-only client can connect to an NFSv3 server
unless the client is smart enough to use NFSv3. The one in Solaris is not
that smart. Neither S10u4, S10u5, OpenSolaris nor any of the Nevada
builds are capable of mounting an NFSv3 share without modifying
/etc/default/nfs.

Hack /etc/default/nfs and the Solaris client easily mounts the NFSv3 share.