Date: Mon, 7 Oct 2002 09:48:16 +0930 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Robert Watson <rwatson@freebsd.org> Cc: fergus <ttz@blahdeblah.demon.co.uk>, current <freebsd-current@freebsd.org> Subject: Re: kernel panic from vinum during 'restore' Message-ID: <20021007001816.GD12610@wantadilla.lemis.com> In-Reply-To: <Pine.NEB.3.96L.1021006182258.5940F-100000@fledge.watson.org> References: <20021006173133.GA1186@pooh.blahdeblah.demon.co.uk> <Pine.NEB.3.96L.1021006182258.5940F-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, 6 October 2002 at 18:25:08 -0400, Robert Watson wrote: > > On Sun, 6 Oct 2002, fergus wrote: > >> i have a crash dump for this now if anyone is interested. it's not >> exactly the same trace as it seems to originate from a VOP_LINK request >> this time but i guess it's the same problem. > > To be honest, it sounds like something is simply leaking kernel > memory/address space. What you might want to do is have vmstat -m looping > with a sleep in the background, writing to a log file, then see if you can > figure out which number goes up, but never down.. Maybe something is > leaking memory that previously wasn't. You shouldn't even need to crash > the machine to figure it out, I think (although with a serious kernel > memory leak scenario, that might be unavoidable :-). As a reminder, Vinum keeps track of its kernel memory allocation, and you can view it at any time with 'vinum info -v'. In a typical scenario, you'd expect to see about 50 to 100 kB allocated in about 50 chunks. If you see more, send me the list and I'll check if it looks like a memory leak. I haven't seen any for a long time. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021007001816.GD12610>