From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 09:03:30 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 13FB2DFA for ; Thu, 24 Jul 2014 09:03:30 +0000 (UTC) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8FE6C2766 for ; Thu, 24 Jul 2014 09:03:29 +0000 (UTC) Received: from mh0.gentlemail.de (mh0.gentlemail.de [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id s6O93PFA055631; Thu, 24 Jul 2014 11:03:25 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id E7258352A; Thu, 24 Jul 2014 11:03:24 +0200 (CEST) Message-ID: <53D0CBD6.1020708@omnilan.de> Date: Thu, 24 Jul 2014 11:03:18 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Rick Macklem Subject: Re: nfsd server cache flooded, try to increase nfsrc_floodlevel References: <1578548312.7148700.1375964458716.JavaMail.root@uoguelph.ca> In-Reply-To: <1578548312.7148700.1375964458716.JavaMail.root@uoguelph.ca> X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigD06AF3F8B028172AC0625C8B" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Thu, 24 Jul 2014 11:03:25 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2014 09:03:30 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD06AF3F8B028172AC0625C8B Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Bez=FCglich Rick Macklem's Nachricht vom 08.08.2013 14:20 (localtime): > Lars Eggert wrote: >> Hi, >> >> every few days or so, my -STABLE NFS server (v3 and v4) gets wedged >> with a ton of messages about "nfsd server cache flooded, try to >> increase nfsrc_floodlevel" in the log, and nfsstat shows TCPPeak at >> 16385. It requires a reboot to unwedge, restarting the server does >> not help. >> >> The clients are (mostly) six -CURRENT nfsv4 boxes that netboot from >> the server and mount all drives from there. >> >> I googled around and saw that others have hit this issue, but I >> haven't seen any resolution posted. I guess I can increase >> NFSRVCACHE_FLOODLEVEL in the source, but I wonder if I wouldn't >> simply hit the increase value after a little while longer... >> >> Lars >> > You can either try this patch (which dynamically adjusts nfsrc_floodlev= el > along with handling a variety of overhead issues for the DRC under heav= y load): > http://people.freebsd.org/~rmacklem/drc4.patch > > or just bump it up a bunch. The default value was safe for a server wit= h 256Mbytes > of ram and a default mbuf cluster limit. The only thing you might have = to do > along with bumping NFSRC_FLOODLEVEL up is increasing kern.ipc.mbcluster= s. > > The variant of the above patch will make it into head someday, once I m= erge > in changes from ivoras@'s similar patch and confer with him about it. Dear all, regarding the conversation from last year - quoted above, I think I found the mentioned patch (it's variants) MFCd in r255532 (from http://svnweb.freebsd.org/base?view=3Drevision&revision=3D25433= 7), so it's included in 9.3-RELEASE. Unfortunately I'm still having the nfsrc_floodlevel problem with OpenOwner=3D16385, CacheSize=3D16385 (in nfsstat -e -s) in my production environment under 9.3-RELEASE-amd64. Extremely light load on the server (2 (FreeBSD8/9) clients), but the building client (nfsv4) locks up frequently. It mounts 'home' and 'ports/ports' via NFSv4 (this time, 'make index' in nfs-mounted /usr/ports killed the nfsv4server). I found another interesting 3 years old patch/thread, which seems never beeing comitted: http://lists.freebsd.org/pipermail/freebsd-fs/2011-July/012016.html I don't really understand all these details of nfs(v4), but I observe problems with regular usage, so I wanted to ask if there are new findings regarding the "nfsd server cache flooded, try to increase nfsrc_floodlevel" messages (while 'nfsrc_floodlevel' doesn't seem to be tunable in 9.3). To my understanding, it's a problem on the server side, right? Is the fix from 3 years back still adequate (does apply with view offsets only to 9.3)? I'm currently testing 9.3-RELEASE+noopen.patch, but it usually took two or three days until the client locked up (hadn't looked for the reason before the last issue, nfs(v4) was brand new reintroduced here) Thanks, -Harry --------------enigD06AF3F8B028172AC0625C8B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlPQy9wACgkQLDqVQ9VXb8gMKgCgzU/4+e2vLZUR+G5uboU7wwxf B84An3tlgzhPO4yeVzWF/R3xSMdfsir5 =q94N -----END PGP SIGNATURE----- --------------enigD06AF3F8B028172AC0625C8B--