From owner-freebsd-hackers Fri Dec 20 2:23:23 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 8590137B401; Fri, 20 Dec 2002 02:23:20 -0800 (PST) Received: from apache.metrocom.ru (www.metrocom.ru [195.5.128.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48C5F43EE5; Fri, 20 Dec 2002 02:23:19 -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 gBKANGiJ026699; Fri, 20 Dec 2002 13:23:16 +0300 (MSK) Received: from localhost (alex@localhost) by apache.metrocom.ru (8.12.6/8.12.6/Submit) with ESMTP id gBKANFab026696; Fri, 20 Dec 2002 13:23:15 +0300 (MSK) X-Authentication-Warning: apache.metrocom.ru: alex owned process doing -bs Date: Fri, 20 Dec 2002 13:23:15 +0300 (MSK) From: Varshavchick Alexander To: Maxim Konovalov , Matt Dillon Cc: Dmitry Morozovsky , David Schultz , Terry Lambert , Subject: Invalid FFC node allocation algorithm (Was: maxusers and random system freezes) In-Reply-To: <20021219170203.F67349@news1.macomnet.ru> 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 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. *********** Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) FFS node 361722 90431K 90431K 102400K 9156217 0 0 256 kern.maxvnodes: 229508 kern.minvnodes: 57377 vm.stats.vm.v_vnodein: 206541 vm.stats.vm.v_vnodeout: 0 vm.stats.vm.v_vnodepgsin: 838385 vm.stats.vm.v_vnodepgsout: 0 debug.sizeof.vnode: 168 debug.numvnodes: 361773 debug.wantfreevnodes: 25 debug.freevnodes: 23 *********** Kern/32672: ***** State-Changed-From-To: open->closed .... This is believed to be fixed in -stable (and thus for the upcoming 4.5 release). ***** So as it seems, it's really not fixed there... Regards ---- Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)118-3322, 118-3115(fax) On Thu, 19 Dec 2002, Maxim Konovalov wrote: > Date: Thu, 19 Dec 2002 17:05:14 +0300 (MSK) > From: Maxim Konovalov > To: Varshavchick Alexander > Cc: Dmitry Morozovsky , > David Schultz , > Terry Lambert , > Subject: Re: maxusers and random system freezes > > On 16:51+0300, Dec 19, 2002, Varshavchick Alexander wrote: > > > On Thu, 19 Dec 2002, Maxim Konovalov wrote: > > [...] > > > > [ Trim -questions ] > > > > > > On 16:21+0300, Dec 19, 2002, Varshavchick Alexander wrote: > > > > > > > There seems to be archive posts already on the subject, the most > > > > informative of them is here: > > > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=1093170+1102546+/usr/local/www/db/text/2001/freebsd-stable/20010923.freebsd-stable > > > > > > > > Did this issue got solved somehow? More specifically, how the size of the > > > > FFS node malloc area can be increased? > > > > > > Sounds like kern/32672. > > > > Yes it does, but the problem seems to remain in 4.5-STABLE, how can it be > > patched? > > > > ***** > > State-Changed-From-To: open->closed > > .... > > This is believed to be fixed in -stable (and thus for the upcoming 4.5 > > release). The problem was that the vnode/inode reclamation system depends > > on the VM system running out of memory and having to free vnodes/inodes up. > > Machines with large amounts of ram, however, will often run the malloc > > bucket for vnodes or inodes out before they run out of memory. > > > > Our solution is to enforce the kern.maxvnodes limit by proactively reclaiming > > vnodes/inodes when the limit is reached, even if there is still lots of free > > memory. > > ***** > > > > Can you point me to a code performing it, if it's fixed in the latest > > release? > > We should CC: Matt Dillon, dillon@. Could you please summarize all > information and send a complete bug report to -hackers? > > [...] > > -- > Maxim Konovalov, MAcomnet, Internet Dept., system engineer > phone: +7 (095) 796-9079, mailto:maxim@macomnet.ru > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message