From owner-freebsd-hackers Thu Dec 19 6: 6: 2 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 E9AE337B401 for ; Thu, 19 Dec 2002 06:05:59 -0800 (PST) Received: from relay1.macomnet.ru (relay1.macomnet.ru [195.128.64.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DF0F43ED8 for ; Thu, 19 Dec 2002 06:05:58 -0800 (PST) (envelope-from maxim@macomnet.ru) Received: from news1.macomnet.ru (news1.macomnet.ru [195.128.64.14]) by relay1.macomnet.ru (8.11.6/8.11.6) with ESMTP id gBJE5EZ7035835; Thu, 19 Dec 2002 17:05:14 +0300 (MSK) 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 In-Reply-To: Message-ID: <20021219170203.F67349@news1.macomnet.ru> References: 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 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