Are the nfsd versions that you're setting being respected? You can > check with "rpcinfo -s" or "cat /proc/fs/nfsd/versions". >
Yep; # cat /proc/fs/nfsd/versions -2 +3 +4 +4.1 +4.2 > You can change the number of threads on the fly with "echo 1 > > /proc/fs/nfsd/threads". > That works too, but then; # ps -ef | grep nfsd root 1454 1426 0 12:47 pts/0 00:00:00 grep --colour=auto nfsd root 23546 2 0 Jul19 ? 00:00:00 [nfsd4_callbacks] root 23548 2 0 Jul19 ? 00:00:00 [nfsd] # strace -p 23548 strace: attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted > I don't use systemd on Gentoo but for the nfs-utils upstream-shipped > systemd units that I think that Gentoo's using, you have to re-run > nfs-config.service - or run the script that it calls - in order to > update the "/run/sysconfig/nfs-utils" environment file that's sourced > by the nfs-server.service unit. > In /usr/lib/systemd/system/nfs-server.service [Service] EnvironmentFile=/etc/conf.d/nfs Does "/var/lib/nfs/v4recovery/" exist? > > No # ls /var/lib/nfs/ etab export-lock rmtab rpc_pipefs sm sm.bak state xtab Does adding the client to "/etc/hosts" - or to your reverse dns zone - > eliminate the delay? > > DNS is setup and both client and server can forward and reverse lookup each other.
