|
From: Helmut J. <jar...@ig...> - 2004-12-21 09:37:12
|
On 20 Dec, David Gesswein wrote:
>> That's what the restore -V option is there for.
>>
>> Correction: looking at the source I see that -V is used only when
>> reading multi-volume *compressed* dumps (and indeed, this is what I
>> use myself). I wonder whether uncompressed dumps need a special treatement
>> or not...
>>
> Works fine if I compress with -z1. Since the data wasn't too compressable I
> had decided to not compress. With compression does a read error make
> the rest of the backup unreadable or does the decompression resync?
>
> Might be good to document the interaction of -V and compression if not
> done already.
1st) you can take -y (lzo compression) which is really fast
2nd) with -y each block is compressed individually, i.e.
if some block has a read error cdrecord might continue,
but the compressed block contains a length field.
I am not sure what will happen if this is completely
unreasonable.
--
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany
|