From owner-freebsd-net@FreeBSD.ORG Wed May 24 19:53:16 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98F8D16A435 for ; Wed, 24 May 2006 19:53:16 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAEF443D76 for ; Wed, 24 May 2006 19:53:09 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 92C961A4EAB; Wed, 24 May 2006 12:53:09 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 054B151616; Wed, 24 May 2006 15:53:08 -0400 (EDT) Date: Wed, 24 May 2006 15:53:08 -0400 From: Kris Kennaway To: Marko Lerota Message-ID: <20060524195308.GA87701@xor.obsecurity.org> References: <20060523135201.75470.qmail@web36303.mail.mud.yahoo.com> <86vervva0x.fsf@redcloud.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99" Content-Disposition: inline In-Reply-To: <86vervva0x.fsf@redcloud.local> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org, Nash Nipples Subject: Re: nfsd and CPU/performance problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 19:53:18 -0000 --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 24, 2006 at 03:15:42PM +0200, Marko Lerota wrote: > Nash Nipples writes: >=20 > > Hi Marko, > > > > Actually i dont find that load critical. I think those lines well tell = that actually the process is running 581m42s and now it utilizes 13.48%=20 >=20 > Sometimes it was 80% >=20 > > which sounds like a "kernel tuning issue" if you have excluded nfsserve= r out of your kernel config last time u were compiling it. if you didnt jus= t skip this part at this time. > > please make sure that the following lines do exist > > options NFSCLIENT # Network Filesystem Client > > options NFSSERVER # Network Filesystem Server > > options NFS_ROOT # NFS usable as /, requires= NFSCLIENT >=20 > No=20 >=20 > > These options are added in rc.conf and server now works correctly. =20 > > > > rpc_lockd_enable=3D"YES" > > rpc_statd_enable=3D"YES" >=20 > It didn't help. See discussion on stable@ for what is believed to be the problem. Backing out the changes to vfs_lookup.c would work around the problem for now (although it reintroduces other bugs). > Now cpu is like it should be, but BSD crashes twice a day=20 > with nothing in logs that I can find. What do you mean "crashes" then? Do you need to configure crashdumps as described in the handbook and developers' handbook? Kris --5vNYLRcllDrimb99 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEdLmkWry0BWjoQKURAl9KAKCNtWcZ0haEzvxoiVaRmSMew+pevgCeLhR2 sYBKAFTj+ODVkalmykt16kI= =/kSc -----END PGP SIGNATURE----- --5vNYLRcllDrimb99--