I changed the NFS back to v3, set it to use TCP rather than UDP in fstab, and
everything is happy now.
Kris Kennaway-3 wrote:
>
> mikeco wrote:
>> Where is it specified whether to use UDP or TCP for NFS clients? I never
>> explicitly set it to one or the other.
>
> See the manpage. It defaul
mikeco wrote:
Where is it specified whether to use UDP or TCP for NFS clients? I never
explicitly set it to one or the other.
See the manpage. It defaults to UDP in 7.0 and older, although the
default will soon change to TCP mounts since UDP mounts are no longer
appropriate in most cases.
Where is it specified whether to use UDP or TCP for NFS clients? I never
explicitly set it to one or the other.
Kris Kennaway-3 wrote:
>
> You could try TCP mounts in case they are less broken on the
> server side. They are recommended anyway.
>
--
View this message in context:
http://ww
mikeco wrote:
I've tried mounting it as nfs rather than nfs4, but it just scrolls an error
until I send a break:
mount -t nfs cnfs:/export /nfs
[udp] cnfs:/export: NFSPROC_NULL: RPC: Timed out
That says the server is failing to respond to the client's mount
request. You could try TCP mounts i
I've tried mounting it as nfs rather than nfs4, but it just scrolls an error
until I send a break:
mount -t nfs cnfs:/export /nfs
[udp] cnfs:/export: NFSPROC_NULL: RPC: Timed out
An rpcinfo of the NFS server shows that it should support versions 2-4:
$ rpcinfo -p cnfs | grep nfs
132
mikeco wrote:
I have mounted an NFS4 filesystem shared by a Solaris 10 cluster environment
and am able to browse all of the files, but I cannot touch anything on the
filesystem because of all of the user and group permissions being off.
Here's my fstab entry:
cnfs:/export /nfsnfs4
