Date: Mon, 18 Apr 2016 16:21:26 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: "Kevin P. Neal" <kpn@neutralgood.org> Cc: freebsd-questions@freebsd.org Subject: Re: tool for mapping away bad blocks on an external disk Message-ID: <alpine.BSF.2.20.1604181620531.68720@wonkity.com> In-Reply-To: <20160418204526.GA86917@neutralgood.org> References: <20160417072641.GA2358@c720-r292778-amd64> <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> <alpine.BSF.2.20.1604171023510.30232@wonkity.com> <nf0h0u$5ij$1@ger.gmane.org> <alpine.BSF.2.20.1604171136320.30232@wonkity.com> <20160418065534.GA2198@c720-r292778-amd64> <20160418204526.GA86917@neutralgood.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 18 Apr 2016, Kevin P. Neal wrote: > On Mon, Apr 18, 2016 at 08:55:34AM +0200, Matthias Apitz wrote: >> >> Thanks for all the hints; I started last night with overwriting the full >> disk with: >> >> # dd conv=noerror if=/dev/zero of=/dev/da0 bs=1m > > Just curious: Does anyone know what happens when there is not enough space > at the end of a disk (or tape) to write the entire block? Does a partial > block get written, or does no block get written? It writes the partial block. Or at least I've never bothered doing anything special, and the checksums work out. > It is because I don't know what happens that I usually pick a block size > that is mathematically factored out from the number of blocks on the disk > (and then multiplied by the number of bytes in a block obviously). You work too hard. :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1604181620531.68720>