Date: Sun, 8 Apr 2018 14:24:40 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: =?iso-8859-1?Q?BERTRAND_Jo=EBl?= <joel.bertrand@systella.fr>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: [diskless] pkg takes 100% of a CPU Message-ID: <YQBPR0101MB1042C6F885A261A1C6FCE187DDB80@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <72ccb066-5238-da87-cb22-642c1995caef@systella.fr> References: <aa289e46-170e-760b-c32c-e67bc37ed888@systella.fr> <CAHEMsqaMUWwj08y=oLCiKf3i=GWi=9kzcJ82v69i_50LUpF4fw@mail.gmail.com> <d1187041-65ca-565f-187e-8d5e9afd2210@systella.fr> <1523110791.40504.15.camel@freebsd.org> <20180408131104.117b849278667b57ca51b223@yahoo.es>, <72ccb066-5238-da87-cb22-642c1995caef@systella.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
BERTRAND Jo=EBl wrote: [stuff snipped] > All filesystems are mounted from NetBSD server : > >root@pythagore:/var # mount >192.168.10.128:/srv/pythagore on / (nfs, asynchronous) >devfs on /dev (devfs, local, multilabel) >procfs on /proc (procfs, local) >fdescfs on /dev/fd (fdescfs) >192.168.10.128:/home on /home (nfs, asynchronous) Just fyi, "nfsstat -m" on the client will show you what NFS mount options are actually in use. >root@pythagore:/var # cat /etc/fstab ># Device Mountpoint FStype Options Dump Pass# >192.168.10.128:/srv/pythagore / nfs nfsv3,tcp,soft,intr,rw,async,nolockd I'd suggest you try without the "soft,intr" options. When those are set, a system call like write(2) can return with EINTR and very few (if any) applications handle that correctly. [more stuff snipped] > On server, /var/log/messages are full of : >Apr 8 13:40:49 legendre rpc.lockd: duplicate lock from hilbert.45141 >Apr 8 13:40:49 legendre rpc.lockd: no matching entry for hilbert >Apr 8 13:40:52 legendre rpc.lockd: duplicate lock from pythagore.68734 >Apr 8 13:40:52 legendre rpc.lockd: duplicate lock from pythagore.68734 >Apr 8 13:40:52 legendre rpc.lockd: no matching entry for pythagore >Apr 8 13:40:52 legendre rpc.lockd: no matching entry for pythagore >Apr 8 13:40:55 legendre rpc.lockd: duplicate lock from pythagore.68734 > >even if all filesystems are mounted with nolockd option. If you use "nolockd" on all mounts, you do not need to run rpc.lockd or rpc.statd, which is what I prefer. (The NLM and NSM protocols were undocume= nted and fundamentally broken. Eventually they were published in an X/Open XNFS manual, but it was a vague 2 page summary. The only real doc would be the OpenSolaris implementation. NFSv4 does a much better job of locking, so if = you need the locks to be visible to other clients, that is what I'd suggest= . rick=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQBPR0101MB1042C6F885A261A1C6FCE187DDB80>