On Sunday, 18 August 2019 09:30:36 BST Adam Carter wrote: > Is the output of 'mount | grep nfs' the same on the two client machines?
$ mount | grep nfs nfsd on /proc/fs/nfsd type nfsd (rw,nosuid,nodev,noexec,relatime) It's the same on both clients. In the chroots, I see: atom / # mount | grep nfs 192.168.1.2:/usr/portage on /usr/portage type nfs (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.2,mountvers=3,mountport=32767,mountproto=udp,local_lock=none,addr=192.168.1.2) (That's the one that works right) clrn / # mount | grep nfs 192.168.1.4:/usr/portage on /usr/portage type nfs (rw,relatime,vers=3,rsize=1024,wsize=1024,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.4,mountvers=3,mountport=32767,mountproto=udp,local_lock=none,addr=192.168.1.4) The only differences I can see are the IP addresses (of course) and the rsize and wsize; the good one has 128K, the other 1K. I'd better look into that, though it doesn't look like the problem. The good client is a 32-bit single- core Atom, the other is a 64-bit quad-core Celeron. /etc/conf.d/nfs is the same on both clients: OPTS_RPC_NFSD="1" OPTS_RPC_MOUNTD="-p 32767" OPTS_RPC_STATD="-p 32765 -o 32766" OPTS_RPC_IDMAPD="" OPTS_RPC_GSSD="" OPTS_RPC_SVCGSSD="" OPTS_RPC_RQUOTAD="" EXPORTFS_TIMEOUT=30 Any other ideas? -- Regards, Peter.
