lzip/lziprecover
1
0
Fork 0
Code Issues Activity

Merging upstream version 1.16~pre2.

Browse source 
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
Daniel Baumann 2025-02-21 11:20:27 +01:00
parent bfc3807823
commit 2fa5af17f3
Signed by: daniel
GPG key ID: FBB4F0E80A80222F
19 changed files with 455 additions and 205 deletions
Download patch file Download diff file Expand all files Collapse all files

41
doc/lziprecover.info
View file

@ -12,7 +12,7 @@ File: lziprecover.info, Node: Top, Next: Introduction, Up: (dir)
Lziprecover Manual
******************
This manual is for Lziprecover (version 1.16-pre1, 5 April 2014).
This manual is for Lziprecover (version 1.16-pre2, 25 May 2014).
* Menu:
@ -248,17 +248,26 @@ File: lziprecover.info, Node: Repairing files, Next: Merging files, Prev: Inv
3 Repairing files
*****************
Lziprecover is able to repair files with small errors (up to one byte
error per member). The error may be located anywhere in the file except
in the header (first 6 bytes of each member) or in the 'Member size'
field of the trailer (last 8 bytes of each member). This makes lzip
files resistant to bit-flip, one of the most common forms of data
Lziprecover is usually able to repair files with small errors (up to one
byte error per member). The error may be located anywhere in the file
except in the header (first 6 bytes of each member) or in the 'Member
size' field of the trailer (last 8 bytes of each member). This makes
lzip files resistant to bit-flip, one of the most common forms of data
corruption.
Bit-flip happens when one bit in the file is changed from 0 to 1 or
vice versa. It may be caused by bad RAM or even by natural radiation. I
have seen a case of bit-flip in a file stored in an USB flash drive.
Repairing a file can take some time. Small files or files with the
error located near the beginning can be repaired in a few seconds. But
repairing a large file compressed with a large dictionary size and with
the error located far from the beginning, can take hours.
On the other hand, errors located near the beginning of the file
cause much more loss of data than errors located near the end. So
lziprecover repairs more efficiently the worst errors.

File: lziprecover.info, Node: Merging files, Next: File format, Prev: Repairing files, Up: Top
@ -552,16 +561,16 @@ Concept index

Tag Table:
Node: Top226
Node: Introduction1100
Node: Invoking lziprecover3858
Node: Repairing files9296
Node: Merging files10015
Node: File format11786
Node: Examples14296
Ref: ddrescue-example15497
Node: Unzcrash16606
Node: Problems18978
Node: Concept index19528
Node: Introduction1099
Node: Invoking lziprecover3857
Node: Repairing files9295
Node: Merging files10485
Node: File format12256
Node: Examples14766
Ref: ddrescue-example15967
Node: Unzcrash17076
Node: Problems19448
Node: Concept index19998

End Tag Table