1 |
Are the nfsd versions that you're setting being respected? You can |
2 |
|
3 |
> check with "rpcinfo -s" or "cat /proc/fs/nfsd/versions". |
4 |
> |
5 |
|
6 |
Yep; |
7 |
# cat /proc/fs/nfsd/versions |
8 |
-2 +3 +4 +4.1 +4.2 |
9 |
|
10 |
|
11 |
> You can change the number of threads on the fly with "echo 1 > |
12 |
> /proc/fs/nfsd/threads". |
13 |
> |
14 |
|
15 |
That works too, but then; |
16 |
# ps -ef | grep nfsd |
17 |
root 1454 1426 0 12:47 pts/0 00:00:00 grep --colour=auto nfsd |
18 |
root 23546 2 0 Jul19 ? 00:00:00 [nfsd4_callbacks] |
19 |
root 23548 2 0 Jul19 ? 00:00:00 [nfsd] |
20 |
# strace -p 23548 |
21 |
strace: attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted |
22 |
|
23 |
|
24 |
> I don't use systemd on Gentoo but for the nfs-utils upstream-shipped |
25 |
> systemd units that I think that Gentoo's using, you have to re-run |
26 |
> nfs-config.service - or run the script that it calls - in order to |
27 |
> update the "/run/sysconfig/nfs-utils" environment file that's sourced |
28 |
> by the nfs-server.service unit. |
29 |
> |
30 |
|
31 |
In /usr/lib/systemd/system/nfs-server.service |
32 |
[Service] |
33 |
EnvironmentFile=/etc/conf.d/nfs |
34 |
|
35 |
Does "/var/lib/nfs/v4recovery/" exist? |
36 |
> |
37 |
> |
38 |
No |
39 |
# ls /var/lib/nfs/ |
40 |
etab export-lock rmtab rpc_pipefs sm sm.bak state xtab |
41 |
|
42 |
Does adding the client to "/etc/hosts" - or to your reverse dns zone - |
43 |
> eliminate the delay? |
44 |
> |
45 |
> DNS is setup and both client and server can forward and reverse lookup |
46 |
each other. |