Date: Thu, 11 Sep 2003 00:02:01 +0300 From: Tomi Vainio - Sun Finland <Tomi.Vainio@Sun.COM> To: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Cc: freebsd-current@freebsd.org Subject: Re: ufs related panic with latest current Message-ID: <16223.37193.123878.704675@ultrahot.finland.sun.com> In-Reply-To: <xzp3cf474ga.fsf@dwp.des.no> References: <16222.8328.482125.571191@ultrahot.finland.sun.com> <16222.14948.423489.596523@ultrahot.finland.sun.com> <20030910112539.F53623@carver.gumbysoft.com> <16223.32410.556709.818592@ultrahot.finland.sun.com> <xzp7k4g75p9.fsf@dwp.des.no> <16223.35291.354753.437544@ultrahot.finland.sun.com> <xzp3cf474ga.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smørgrav writes: > > The backtrace you showed seems to indicate that the panic happened > somewhere in the softupdates code, but IIRC that code has a fairly > conservative built-in limit on memory consumption and degrades > gracefully when it hits that limit. It's likely that something else > gobbled up all available kernel memory, and the mallloc() call from > softupdates was simply the straw that broke the camel's back. > > If you have a serial console hooked up, you could try running > > while :; do vmstat -m ; sleep 1 ; done > Second trace didn't have anything to do with fs only fork system calls there so your expanation sounds reasonable. We probably don't see this problem again because system now has enough memory (256M). Tomppa
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16223.37193.123878.704675>