From owner-freebsd-hackers Fri Jun 13 09:42:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA07085 for hackers-outgoing; Fri, 13 Jun 1997 09:42:12 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA07076 for ; Fri, 13 Jun 1997 09:42:08 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA11079; Fri, 13 Jun 1997 09:34:38 -0700 From: Terry Lambert Message-Id: <199706131634.JAA11079@phaeton.artisoft.com> Subject: Re: dump/restore with compression To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Fri, 13 Jun 1997 09:34:38 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <19970613000752.38538@keltia.freenix.fr> from "Ollivier Robert" at Jun 13, 97 00:07:52 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'd never use any compression -- except hardware-based like DAT's -- > because you can't recover much if your tape have a problem... I'm against > compressed file systems for that very reason too. This depends on the implementation. A correct implementation will use block compression rather than file compression or driver level disk compression to limit the possibility of damage. Block compression also has the advantage that the compression tables are highly sensitive to the type of data, so you don't end up compressing a region with a suboptimal table. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.