From owner-freebsd-current Sun Oct 6 17:18:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9EFAC37B401; Sun, 6 Oct 2002 17:18:20 -0700 (PDT) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E69843E86; Sun, 6 Oct 2002 17:18:19 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 11BFD812E1; Mon, 7 Oct 2002 09:48:16 +0930 (CST) Date: Mon, 7 Oct 2002 09:48:16 +0930 From: Greg 'groggy' Lehey To: Robert Watson Cc: fergus , current Subject: Re: kernel panic from vinum during 'restore' Message-ID: <20021007001816.GD12610@wantadilla.lemis.com> References: <20021006173133.GA1186@pooh.blahdeblah.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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