Date: Sat, 7 Apr 2018 07:35:40 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: Ian Lepore <ian@freebsd.org> Cc: =?ISO-8859-1?Q?BERTRAND_Jo=EBl?= <joel.bertrand@systella.fr>, freebsd-hackers@freebsd.org Subject: Re: [diskless] pkg takes 100% of a CPU Message-ID: <201804071435.w37EZeqw008615@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <1523110791.40504.15.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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).
My understanding of the current broken state of afairs is that pkg
does not work over nfs unless you have proper and full lockd support,
AND set NFS_WITH_PROPER_LOCKING in pkg's environment. This really
really really just needs to work without a lot of fuss out of the
box.
The /etc/rc.initdiskless is presenty (11.x and later) in a usable
state, though it has some issues if your /usr is seperate from /,
and you have to override the default size of /var due to bloat,
though I think the sizes of all the tmpfs's got bumped in ^head/.
I had a very nice working iPXE based boot menu system that you
could boot all of {10|11|12-snaps}{i386|amd54}, but it is for
some strange reason having a problem with the NFS load of the
kernel going at an abismal pace, like 10 to 15 minutes to load
the kernel. Stuff before and after that is normal speed. I believe
this to be my fault, I changed something some place, and it broke,
and I did not notice for a good long time. Now I do not know
what it was that I changed that broken it :-(.
The only real special thing in the above setup was a pxeboot that
I got from a very specific point in time that has a nfsroot fix
in it, without that you can not easily override the nfsroot ip:path
from iPXE menu. /boot/pxeboot before and after this specific
version is/was broke (since my test system is borked I can not
test ^/heads latest pxeboot).
Regards,
--
Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201804071435.w37EZeqw008615>