From owner-freebsd-hackers Mon May 26 09:43:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA27896 for hackers-outgoing; Mon, 26 May 1997 09:43:39 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA27884 for ; Mon, 26 May 1997 09:43:34 -0700 (PDT) Received: from localhost (tom@localhost) by misery.sdf.com (8.8.5/8.8.5) with SMTP id JAA04537; Mon, 26 May 1997 09:40:07 -0700 (PDT) Date: Mon, 26 May 1997 09:40:06 -0700 (PDT) From: Tom Samplonius To: John Hay cc: Andre Albsmeier , hackers@FreeBSD.ORG Subject: Re: vm problems on 2.2, 2.1.7 works In-Reply-To: <199705261412.QAA07764@zibbi.mikom.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 26 May 1997, John Hay wrote: > Hmmm. This looks a lot like the problem I have on my news server. > It will run ok for a while and then suddenly start to use up all > of the swap. According to top and ps no process is using that > memory, but if I kill innd quick enough all will be ok. So now > I have a script that runs every minute and kill and restart innd > as soon as the swap usage go over some value. Not nice, but it > works until someone find this thingy. Doesn't happen everywhere: I have a 2.2.1 system running innd, and the innd process has been running since Apr29 (almost a month), without any problems. The server is only moderately busy: it accept 279K articles yesterday, and feed out 394K articles. Tom > John > -- > John Hay -- John.Hay@mikom.csir.co.za > > > Hi, > > > > I am running FreeBSD 2.2-STABLE on a 32MB system. When using > > procmail to deliver large mails, procmail dies with a > > "out of memory" message. After that, the system is either in > > an undefined state (producing messages as "junk pointer, too > > low to make sense.") or freezes completely. > > When running a high priority "top" in another window, I see > > the swap being used growing constantly until all of it is > > used. This is reproducable on different HW. > > However, on 2.1.7 systems everything works great. > > > > Here are some results from my tests: > > > > System Version RAM SWAP Mail Size Status > > ============================================================== > > 486-66 2.1.7 12M 20M 8M/12M/16M OK > > 486-120 2.1.7 20M 72M 8M/12M/16M OK > > PPro-200 2.1.7 64M 300M 8M/12M/16M OK > > > > PPro-200 2.2 64M 300M 8M/12M OK > > PPro-200 2.2 64M 300M 16M FAIL > > P5-166 2.2 32M 150M 8M/12M/16M FAIL > > P5-166 2.2 64M 150M 8M/12M OK > > P5-166 2.2 64M 150M 16M FAIL > > > > I suspect a problem in the vm system in 2.2 but have no idea > > how to fix it. However, I (and others, who confirmed it via > > email) can reproduce it... So if I should try something, tell > > me. > > > > Thanks for any hints > > > > -Andre > > > > >