Date: Wed, 6 Oct 2004 17:04:30 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Vlad <marchenko@gmail.com> Cc: Marc UBM Bocklet <ubm@u-boot-man.de> Subject: Re: [BETA7-panic] sodealloc(): so_count 1 Message-ID: <20041006220430.GD3848@dan.emsphone.com> In-Reply-To: <cd70c68104100614533d3237e6@mail.gmail.com> References: <20041006015131.10116be7.ubm@u-boot-man.de> <cd70c68104100517074a5cebf2@mail.gmail.com> <20041006090104.06710d85.ubm@u-boot-man.de> <20041006154137.GJ47017@green.homeunix.org> <20041006203220.7f8e7b8a.ubm@u-boot-man.de> <20041006192518.GM47017@green.homeunix.org> <cd70c681041006125527e69bcd@mail.gmail.com> <20041006202143.GA3848@dan.emsphone.com> <cd70c68104100614533d3237e6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041006220430.GD3848>