nfsd: cant register svc name - TrueNAS Jul 23 10:18:03 audhumla notifier: nfsuserd not running? Jul 23 10:18:07 audhumla notifier: Starting nfsuserd Jul 23 10:18:07 audhumla notifier: Starting nfsd Jul 23 10:18:07 audhumla nfsd: can't register svc name Looks like nfsd protests on not finding 10 8 0 1 bind address? I'll try and disable that one to see what happens
nfsd question | TrueNAS Community The attached is the screenshot from my another truenas scale build there are lots of nfsd running in parellel, but I didn't see another nfsd in my current core build So I am confused if they should looks the same on both core and scale As there is a number of server configuration in the nfsd service on core and scale both, it's default is 16
NFS Port 2049 is blocked and cant be used - TrueNAS Nov 16 05:42:33 rpc nfsd [190051]: rpc nfsd: unable to bind AF_INET TCP socket: errno 98 (Address already in use) Nov 16 05:42:33 rpc nfsd [190051]: rpc nfsd: unable to set any sockets for nfsd Nov 16 05:42:33 systemd [1]: nfs-server service: Main process exited, code=exited, status=1 FAILURE Nov 16 05:42:33 systemd [1]: nfs-server service
Setting vfs. nfsd. srvmaxio in Tunables - TrueNAS A sysctl called vfs nfsd srvmaxio has been added that can be used to increase the NFS server’s maximum I O size from 128Kbytes to any power of 2 up to 1Mbyte It can only be set when the nfsd threads are not running, and will normally require an increase in kern ipc maxsockbuf to at least the value recommended by the console log message generated when setting vfs nfsd srvmaxio is first
vfs. nfsd. highwater tuning | TrueNAS Community So, I increased vfs nfsd tcphighwater in the Web Interface by going to System->Tunables and clicking the Add Button Then I created a sysctl variable named vfs nfsd tcphighwater with a value of 300,000 This fixed the problem My question to the community is what are the possible repercussions of this change
nfsd thread stuck | TrueNAS Community I'm running 9 10 2-U3 serving nfs to a couple dozen linux clients over a 10Gb (copper) network Under heavy load, all the clients seem to get stuck when doing file moves (rename) and on the file server I see a single nfsd thread eating 100% cpu for many (>10) minutes and none of the other nfsd
Optimizing NFS Number of servers | TrueNAS Community However, running sysctl vfs nfsd threads reflects the value specified in the "Number of servers" setting in the web gui fs nfsd minthreads and vfs nfsd maxthreads are also set to the same value The questions I have at this point are: What is the optimal value for "Number of servers"?