Date: Mon, 3 May 2004 10:45:35 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: freebsd-current@freebsd.org Subject: Re: partial dumps (was Re: Change default dumpdir to /usr/crash?) Message-ID: <20040503154535.GA14109@dan.emsphone.com> In-Reply-To: <16534.21617.310294.982202@grasshopper.cs.duke.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>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (May 03), Andrew Gallatin said: > 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 certainly hope so! Even a 4gb x86 machine that otherwise doesn't need swap at all would benefit, and would reduce the downtime due to the panic needing to write a full dump, and savecore needing to copy it out of swap. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040503154535.GA14109>