Date: Thu, 19 Dec 2002 16:51:45 +0300 (MSK) From: Varshavchick Alexander <alex@metrocom.ru> To: Maxim Konovalov <maxim@macomnet.ru> Cc: Dmitry Morozovsky <marck@rinet.ru>, David Schultz <dschultz@uclink.Berkeley.EDU>, Terry Lambert <tlambert2@mindspring.com>, <freebsd-hackers@FreeBSD.ORG> Subject: Re: maxusers and random system freezes Message-ID: <Pine.GSO.4.33.0212191642201.14913-100000@apache.metrocom.ru> In-Reply-To: <20021219163641.R63500@news1.macomnet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 19 Dec 2002, Maxim Konovalov wrote: > Date: Thu, 19 Dec 2002 16:37:21 +0300 (MSK) > From: Maxim Konovalov <maxim@macomnet.ru> > To: Varshavchick Alexander <alex@metrocom.ru> > Cc: Dmitry Morozovsky <marck@rinet.ru>, > David Schultz <dschultz@uclink.Berkeley.EDU>, > Terry Lambert <tlambert2@mindspring.com>, <freebsd-hackers@FreeBSD.ORG> > Subject: Re: maxusers and random system freezes > > > [ 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? > > > ---- > > Alexander Varshavchick, Metrocom Joint Stock Company > > Phone: (812)118-3322, 118-3115(fax) > > > > On Thu, 19 Dec 2002, Varshavchick Alexander wrote: > > > > > Date: Thu, 19 Dec 2002 13:29:18 +0300 (MSK) > > > From: Varshavchick Alexander <alex@metrocom.ru> > > > To: Dmitry Morozovsky <marck@rinet.ru> > > > Cc: David Schultz <dschultz@uclink.Berkeley.EDU>, > > > Terry Lambert <tlambert2@mindspring.com>, freebsd-questions@FreeBSD.ORG, > > > freebsd-hackers@FreeBSD.ORG > > > Subject: Re: maxusers and random system freezes > > > > > > Hi, > > > > > > Despite the increased KVA space (2G now) and the perfect patch of the > > > pthreads mechanism made by David, the server's lock-ups persist. > > > Comparing this server's vmstat output with some other's which doesn't have > > > the similar problem, I noticed that the FFS node value seems to be > > > abnormally high - 75113K from 102400K possible. What becomes with the > > > system if this value bumps even closer to the limit, and how it can be put > > > into place? > > > > > > And more of it: which other parameters must be examined first? If I'll > > > send the output of vmstat -z and vmstat -m will you look at it please? > > > > > > Thanks a lot, regards > > > > > > ---- > > > Alexander Varshavchick, Metrocom Joint Stock Company > > > Phone: (812)118-3322, 118-3115(fax) > > > > > > On Mon, 9 Dec 2002, Dmitry Morozovsky wrote: > > > > > > > Date: Mon, 9 Dec 2002 22:32:04 +0300 (MSK) > > > > From: Dmitry Morozovsky <marck@rinet.ru> > > > > To: Varshavchick Alexander <alex@metrocom.ru> > > > > Cc: David Schultz <dschultz@uclink.Berkeley.EDU>, > > > > Terry Lambert <tlambert2@mindspring.com>, > > > > <freebsd-questions@FreeBSD.ORG>, <freebsd-hackers@FreeBSD.ORG> > > > > Subject: Re: maxusers and random system freezes > > > > > > > > On Mon, 9 Dec 2002, Varshavchick Alexander wrote: > > > > > > > > VA> the server went to a swap, because it occurs practically instantly, and > > > > VA> this state goes for hours. The system is lacking some resources, or may be > > > > VA> a bug somewhere, can you give any hints to it? > > > > > > > > Hmm, what about logging vmstat/pstat/netstat -m/sysctl vm ? Possibly to remote > > > > machine via remote syslog? > > > > > > > > Sincerely, > > > > D.Marck [DM5020, DM268-RIPE, DM3-RIPN] > > > > ------------------------------------------------------------------------ > > > > *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** > > > > ------------------------------------------------------------------------ > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > -- > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.33.0212191642201.14913-100000>