1 |
On Sunday, 18 August 2019 09:30:36 BST Adam Carter wrote: |
2 |
|
3 |
> Is the output of 'mount | grep nfs' the same on the two client machines? |
4 |
|
5 |
$ mount | grep nfs |
6 |
nfsd on /proc/fs/nfsd type nfsd (rw,nosuid,nodev,noexec,relatime) |
7 |
|
8 |
It's the same on both clients. |
9 |
|
10 |
In the chroots, I see: |
11 |
|
12 |
atom / # mount | grep nfs |
13 |
192.168.1.2:/usr/portage on /usr/portage type nfs |
14 |
(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) |
15 |
|
16 |
(That's the one that works right) |
17 |
|
18 |
clrn / # mount | grep nfs |
19 |
192.168.1.4:/usr/portage on /usr/portage type nfs |
20 |
(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) |
21 |
|
22 |
The only differences I can see are the IP addresses (of course) and the rsize |
23 |
and wsize; the good one has 128K, the other 1K. I'd better look into that, |
24 |
though it doesn't look like the problem. The good client is a 32-bit single- |
25 |
core Atom, the other is a 64-bit quad-core Celeron. |
26 |
|
27 |
/etc/conf.d/nfs is the same on both clients: |
28 |
OPTS_RPC_NFSD="1" |
29 |
OPTS_RPC_MOUNTD="-p 32767" |
30 |
OPTS_RPC_STATD="-p 32765 -o 32766" |
31 |
OPTS_RPC_IDMAPD="" |
32 |
OPTS_RPC_GSSD="" |
33 |
OPTS_RPC_SVCGSSD="" |
34 |
OPTS_RPC_RQUOTAD="" |
35 |
EXPORTFS_TIMEOUT=30 |
36 |
|
37 |
Any other ideas? |
38 |
|
39 |
-- |
40 |
Regards, |
41 |
Peter. |