From owner-freebsd-current@FreeBSD.ORG Wed Oct 6 22:04:31 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 AC00A16A4CE; Wed, 6 Oct 2004 22:04:31 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C2CA43D3F; Wed, 6 Oct 2004 22:04:31 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.11/8.12.11) id i96M4UFn029263; Wed, 6 Oct 2004 17:04:30 -0500 (CDT) (envelope-from dan) Date: Wed, 6 Oct 2004 17:04:30 -0500 From: Dan Nelson To: Vlad Message-ID: <20041006220430.GD3848@dan.emsphone.com> References: <20041006015131.10116be7.ubm@u-boot-man.de> <20041006090104.06710d85.ubm@u-boot-man.de> <20041006154137.GJ47017@green.homeunix.org> <20041006203220.7f8e7b8a.ubm@u-boot-man.de> <20041006192518.GM47017@green.homeunix.org> <20041006202143.GA3848@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.3-BETA7 X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: current@freebsd.org cc: Marc UBM Bocklet Subject: Re: [BETA7-panic] sodealloc(): so_count 1 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, 06 Oct 2004 22:04:31 -0000 In the last episode (Oct 06), Vlad said: > > If you apply the crashdump_compress patch at > > http://dan.allantgroup.com/FreeBSD/ , you can generate lzop or > > gzip-compressed dumps. lzop will let you dump 1GB of ram into 512MB of > > swap, and gzip will do even better (but is much much slower). > > > > I'll try that. One question: does that code has bounds checking > mechanism, so there will be no data harmed (past swap partition) even > if compressed dump will be bigger than swap partition? Yes. All of the functions that write data end up calling the dump_write() function, which will fail if an attempt is made to write outside the dump device. In addition, the code does a preliminary compress to determine where it should start writing the dump. If that size is larger than your dumpdevice, it will print a "Dump failed. Partition too small." error and won't write to disk at all. -- Dan Nelson dnelson@allantgroup.com