From owner-freebsd-current@FreeBSD.ORG Mon May 3 07:55:22 2004 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 EE82216A4CE for ; Mon, 3 May 2004 07:55:22 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id C34EF43D45 for ; Mon, 3 May 2004 07:55:22 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) i43EtKdl074644; Mon, 3 May 2004 07:55:20 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)i43EtJfB074643; Mon, 3 May 2004 07:55:19 -0700 (PDT) (envelope-from sgk) Date: Mon, 3 May 2004 07:55:19 -0700 From: Steve Kargl To: Andrew Gallatin Message-ID: <20040503145519.GA74546@troutmask.apl.washington.edu> References: <200404301403.50634.past@noc.ntua.gr> <20040430123040.GB30157@melusine.cuivre.fr.eu.org> <20040430211948.GC85783@dragon.nuxi.com> <16534.21617.310294.982202@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16534.21617.310294.982202@grasshopper.cs.duke.edu> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: partial dumps (was Re: Change default dumpdir to /usr/crash?) 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: Mon, 03 May 2004 14:55:23 -0000 On Mon, May 03, 2004 at 10:17:21AM -0400, Andrew Gallatin wrote: > > Another good idea (perhaps in combination with a larger /var) is to > accept and port to -current the Duke "partial dump" patches. These > patches allow the user to optionally dump just the kernel virtual > address space. This results in dumps that are generally less than > 100MB, rather than multiple gigs. > > In nearly all cases, only the kernel address space is needed to > interpret a dump. From what I've seen, this is what Solaris, AIX, and > Tru64 do by default. > > Porting to -current will be non-trivial because of the dump changes > between 4.x and 5.x. If I was to do this, is there any chance that > it could get into the tree? > I would support the integration of the changes. With dual opteron systems capacities of 16 to 24 GB of memory, partial dump goes from a "nice to have feature" to a "we need this feature." -- Steve