From owner-freebsd-hackers  Thu Jun 12 23:13:32 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id XAA13501
          for hackers-outgoing; Thu, 12 Jun 1997 23:13:32 -0700 (PDT)
Received: from misery.sdf.com (misery.sdf.com [204.244.210.193])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA13493
          for <freebsd-hackers@freebsd.org>; Thu, 12 Jun 1997 23:13:25 -0700 (PDT)
Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1)
	id 0wcPZv-0000e5-00; Thu, 12 Jun 1997 23:11:19 -0700
Date: Thu, 12 Jun 1997 23:11:19 -0700 (PDT)
From: Tom Samplonius <tom@sdf.com>
To: Ollivier Robert <roberto@keltia.freenix.fr>
cc: freebsd-hackers@freebsd.org
Subject: Re: dump/restore with compression
In-Reply-To: <19970613000752.38538@keltia.freenix.fr>
Message-ID: <Pine.BSF.3.95q.970612230941.2315A-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Fri, 13 Jun 1997, Ollivier Robert wrote:

...
> 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.

  Not if you do file-by-file compression.  Compressed tar archives have
this problem:  every file after the damaged area is lost.  But if you
compress the files first, then tar them, you can still recover all files
after the damaged area.

...
> -- 
> Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr
> FreeBSD keltia.freenix.fr 3.0-CURRENT #18: Sun Jun  8 15:32:28 CEST 1997
> 
> 

Tom