From owner-freebsd-hackers Fri Dec 20 5:20:27 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4259937B401 for ; Fri, 20 Dec 2002 05:20:26 -0800 (PST) Received: from apache.metrocom.ru (www.metrocom.ru [195.5.128.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AE1143ED8 for ; Fri, 20 Dec 2002 05:20:24 -0800 (PST) (envelope-from alex@metrocom.ru) Received: from apache.metrocom.ru (localhost [127.0.0.1]) by apache.metrocom.ru (8.12.6/8.12.6) with ESMTP id gBKDKIiJ015709; Fri, 20 Dec 2002 16:20:18 +0300 (MSK) Received: from localhost (alex@localhost) by apache.metrocom.ru (8.12.6/8.12.6/Submit) with ESMTP id gBKDKGwi015701; Fri, 20 Dec 2002 16:20:16 +0300 (MSK) X-Authentication-Warning: apache.metrocom.ru: alex owned process doing -bs Date: Fri, 20 Dec 2002 16:20:16 +0300 (MSK) From: Varshavchick Alexander To: Matthew Dillon Cc: Maxim Konovalov , Dmitry Morozovsky , David Schultz , Terry Lambert , Subject: Re: Invalid FFC node allocation algorithm (Was: maxusers and random system freezes) In-Reply-To: <200212201102.gBKB2nLX050734@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 20 Dec 2002, Matthew Dillon wrote: > :Hi, > : > :It seems that kern/32672 is not fixed yet on FreeBSD 4.5-STABLE. > : > :System 4Gb RAM, 4x700MHz > : > :When the system is not using all RAM, the FFS node memory grows up to a > :limit of 102400K which leads to a system deadlocking. > > Well, there was some further work done to the vnode reclamation > code after the 4.5 release. RELENG_4_5 has 1.249.2.23 > RELENG_4_6 has 1.249.2.27. Peter Wemm introduced a major upgrade > to the vnode reclamation in 1.249.2.24. > > I don't think I can really go back and backport this stuff to the > 4.5 branch. If you upgrade to 4.6 or 4.7 and still have the problem > I can look into it (the differences in this particular area of code > between 4.6 and 4.7 are minor and it would be easy to make fixes in > both branches). > > -Matt So, at least a possible cause of the server halts seems to have been cleared. As for now, we'll see if this server can be saved from the block-outs by periodically checking the freevnodes value and running a ram-consuming program to free vnodes if this value is getting too low. Or eventually upgrading to a new version. Thank you for the answer ---- Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)118-3322, 118-3115(fax) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message