Date: Sun, 8 Apr 2018 13:42:34 +0200 From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr> To: freebsd-hackers@freebsd.org Subject: Re: [diskless] pkg takes 100% of a CPU Message-ID: <72ccb066-5238-da87-cb22-642c1995caef@systella.fr> In-Reply-To: <20180408131104.117b849278667b57ca51b223@yahoo.es> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Eduardo Morras via freebsd-hackers a écrit : > On Sat, 07 Apr 2018 08:19:51 -0600 > Ian Lepore <ian@freebsd.org> wrote: > >> On Sat, 2018-04-07 at 11:50 +0200, BERTRAND Jol wrote: >>> Steven Hartland a crit: >>>> >>>> When we?ve seen it using 100% it?s been doing comprehension stuff >>>> which usually finishes you just have to wait. Not sure if that?s >>>> what you?re seeing? >>> Yesterday, I have killed pkg after more than 100 hours of >>> CPU time... >>> >>> Best regards, >>> >>> JB >> >> For me, pkg(8) quit working on systems that have /var/db mounted from >> nfs long ago, maybe as much as a year ago at this point. I mentioned >> it on irc, and was told "It's probably something to do with locking", >> but I already have boot.nfsroot.options="nolockd" in loader.conf >> (because that's pretty much the only option because the rc(8) system >> was broken years ago when it comes to nfsroot). > > Is the db is on netbsd side? If yes, sqlite db over nfs are pita > because nfs lies about file locking. It's true that it works 99% of > time, the problematic part is the 1%. Documentation talks about > incorrect NFS implementation, but a correct implementation can fail too > because network latency, separate memory data between clients and > server or different filesystem semantics; or all of them. 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) 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 0 0 proc /proc procfs rw 0 0 fdesc /dev/fd fdescfs rw 0 0 192.168.10.128:/home /home nfs nfsv3,tcp,soft,intr,rw,async 0 0 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. JB
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?72ccb066-5238-da87-cb22-642c1995caef>