Date: Mon, 26 May 1997 16:43:47 +0200 (CEST) From: Andre Albsmeier <Andre.Albsmeier@mchp.siemens.de> To: jhay@zibbi.mikom.csir.co.za (John Hay) Cc: hackers@FreeBSD.ORG Subject: Re: vm problems on 2.2, 2.1.7 works Message-ID: <199705261443.QAA03605@curry.mchp.siemens.de> In-Reply-To: <199705261412.QAA07764@zibbi.mikom.csir.co.za> from John Hay at "May 26, 97 04:12:48 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. Yes, the same here. The swapspace in use diplayed in top grows to its limits but there is no process using it. procmail stays between 8M and 17M depending on the mail size... This confirmes my thinking, that procmail itself isn't the problem... > > 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 > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705261443.QAA03605>