From owner-freebsd-current@FreeBSD.ORG Wed Apr 16 00:32:58 2003 Return-Path: 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 AB17337B401 for ; Wed, 16 Apr 2003 00:32:58 -0700 (PDT) Received: from mailspool.ops.uunet.co.za (mailspool.ops.uunet.co.za [196.7.0.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FF2543F85 for ; Wed, 16 Apr 2003 00:32:57 -0700 (PDT) (envelope-from ianf@wcom.com) Received: from copernicus.so.cpt1.za.uu.net ([196.30.72.32]) by mailspool.ops.uunet.co.za with esmtp (Exim 3.36 #1) id 195hPH-000G2v-00; Wed, 16 Apr 2003 09:32:35 +0200 Received: from localhost ([127.0.0.1] helo=wcom.com) by copernicus.so.cpt1.za.uu.net with esmtp (Exim 3.36 #1) id 195hPC-000FhV-00; Wed, 16 Apr 2003 09:32:30 +0200 To: Steve Kargl In-reply-to: Your message of "Tue, 15 Apr 2003 14:25:04 MST." <20030415212504.GA17123@troutmask.apl.washington.edu> References: <20030415212504.GA17123@troutmask.apl.washington.edu> From: "Ian Freislich" X-image-url: http://www.digs.iafrica.com/gallery/ian-small.gif X-BOFH: true X-LART: Depleted uranium X-No-Junk-Mail: I do not want to get *any* junk mail. You have been deleted Date: Wed, 16 Apr 2003 09:32:30 +0200 Message-ID: <60356.1050478350@wcom.com> Sender: ianf@wcom.com cc: Poul-Henning Kamp cc: freebsd-current@freebsd.org Subject: Re: Kernel memory leak? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Apr 2003 07:32:58 -0000 Steve Kargl wrote: > On Tue, Apr 15, 2003 at 11:11:46PM +0200, Poul-Henning Kamp wrote: > > In message <55218.1050439220@wcom.com>, "Ian Freislich" writes: > > > > ># There must be a better way to do this > > > > I suggest instead you search for valid superblocks, they have a > > well-defined magic word you could look for. > > > > I even belive I have seen reports of a tool that does it automatically, > > but have no references at hand. So had I, but I didn't expect it to be a port so I didn't find it and I'd had great success with this method last time on a 3.x box, only it didn't panic back then. Statically linked in /sbin would have been nice. > ports/sysutils/ffsrecov Hopefully I'll remember this in a couple of years time when I next have a rush of blood to the head and break my disklabels. However, it wouldn't have shown up this memory leak :/. Ian