Date: Wed, 16 Apr 2003 09:32:30 +0200 From: "Ian Freislich" <ianf@za.uu.net> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-current@freebsd.org Subject: Re: Kernel memory leak? Message-ID: <60356.1050478350@wcom.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?60356.1050478350>