This manual is for Lziprecover (version 1.20-pre1, 4 May 2017).
Copyright © 2009-2017 Antonio Diaz Diaz.
This manual is free documentation: you have unlimited permission to copy, distribute and modify it.
Lziprecover is a data recovery tool and decompressor for files in the lzip compressed data format (.lz). Lziprecover is able to repair slightly damaged files, produce a correct file by merging the good parts of two or more damaged copies, extract data from damaged files, decompress files and test integrity of files.
Lziprecover provides random access to the data in multimember files; it only decompresses the members containing the desired data.
Lziprecover is not a replacement for regular backups, but a last line of defense for the case where the backups are also damaged.
The lzip file format is designed for data sharing and long-term archiving, taking into account both data integrity and decoder availability:
A nice feature of the lzip format is that a corrupt byte is easier to repair the nearer it is from the beginning of the file. Therefore, with the help of lziprecover, losing an entire archive just because of a corrupt byte near the beginning is a thing of the past.
For compressible data, multiple lzip-compressed copies have a better chance of surviving intact than one uncompressed copy using the same amount of storage space.
Lziprecover is able to recover or decompress files produced by any of the compressors in the lzip family; lzip, plzip, minilzip/lzlib, clzip and pdlzip.
If the cause of file corruption is damaged media, the combination GNU ddrescue + lziprecover is the best option for recovering data from multiple damaged copies. See ddrescue-example, for an example.
If a file is too damaged for lziprecover to repair it, all the recoverable data in all members of the file can be extracted with the following command (the resulting file may contain errors and some garbage data may be produced at the end of each member):
lziprecover -D0 -i -o file -q file.lz
When recovering data, lziprecover takes as arguments the names of the damaged files and writes zero or more recovered files depending on the operation selected and whether the recovery succeeded or not. The damaged files themselves are never modified.
When decompressing or testing file integrity, lziprecover behaves like lzip or lunzip.
LANGUAGE NOTE: Uncompressed = not compressed = plain data; it may never have been compressed. Decompressed is used to refer to data which have undergone the process of decompression.
The format for running lziprecover is:
lziprecover [options] [files]
When decompressing or testing, '-' used as a file argument means standard input. It can be mixed with other files and is read just once, the first time it appears in the command line.
Lziprecover supports the following options:
The name of the converted lzip file is derived from that of the original lzma-alone file as follows:
Four formats of range are recognized, 'begin',
'begin-end', 'begin,size', and
',size'. If only begin is specified, end is taken
as the end of the file. If only size is specified, begin is
taken as the beginning of the file. The produced bytes are sent to
standard output unless the '--output' option is used.
The names of the files produced are in the form 'rec01file',
'rec02file', etc, and are designed so that the use of
wildcards in subsequent processing, for example, 'lziprecover -cd rec*file > recovered_data', processes the files in the
correct order. The number of digits used in the names varies depending
on the number of members in 'file'.
Numbers given as arguments to options may be followed by a multiplier and an optional 'B' for "byte".
Table of SI and binary prefixes (unit multipliers):
|k||kilobyte (10^3 = 1000)|||||Ki||kibibyte (2^10 = 1024)
|M||megabyte (10^6)|||||Mi||mebibyte (2^20)
|G||gigabyte (10^9)|||||Gi||gibibyte (2^30)
|T||terabyte (10^12)|||||Ti||tebibyte (2^40)
|P||petabyte (10^15)|||||Pi||pebibyte (2^50)
|E||exabyte (10^18)|||||Ei||exbibyte (2^60)
|Z||zettabyte (10^21)|||||Zi||zebibyte (2^70)
|Y||yottabyte (10^24)|||||Yi||yobibyte (2^80)
Exit status: 0 for a normal exit, 1 for environmental problems (file not found, invalid flags, I/O errors, etc), 2 to indicate a corrupt or invalid input file, 3 for an internal consistency error (eg, bug) which caused lziprecover to panic.
There are 3 main types of data corruption that may cause data loss: single-byte errors, multibyte errors (generally affecting a whole sector in a block device), and total device failure.
Lziprecover protects natively against single-byte errors (see Repairing files), as long as file integrity is checked frequently enough that a second single-byte error does not develop in the same member before the first one is repaired.
Lziprecover also protects against multibyte errors (see Merging files), if at least one backup copy of the file is made.
The only remedy for total device failure is storing backup copies in separate media.
How does lzip compare with gzip and bzip2 with respect to data safety? Let's suppose that you made a backup of your valuable scientific data, compressed it, and stored two copies on separate media. Years later you notice that both copies are corrupt.
If you compressed with gzip and both copies suffer any damage in the data stream, even if it is just one altered bit, the original data can't be recovered.
If you used bzip2, and if the file is large enough to contain more than one compressed data block (usually larger than 900 kB uncompressed), and if no block is damaged in both files, then the data can be manually recovered by splitting the files with bzip2recover, verifying every block and then copying the right blocks in the right order into another file.
But if you used lzip, the data can be automatically recovered as long as the damaged areas don't overlap.
Note that each error in a bzip2 file makes a whole block unusable, but each error in a lzip file only affects the damaged bytes, making it possible to recover a file with thousands of errors.
Lziprecover can repair perfectly most files with small errors (up to one single-byte error per member), without the need of any extra redundance at all. If the reparation is successful, the repaired file will be identical bit for bit to the original. This makes lzip files resistant to bit-flip, one of the most common forms of data corruption.
The error may be located anywhere in the file except in the first 5 bytes of each member header or in the 'Member size' field of the trailer (last 8 bytes of each member). If the error is in the header it can be easily repaired with a text editor like GNU Moe (see File format). If the error is in the member size, it is enough to ignore the message about 'bad member size' when decompressing.
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 on an USB flash drive.
One byte may seem small, but most file corruptions not produced by transmission errors or I/O errors just affect one byte, or even one bit, of the file. Also, unlike magnetic media, where errors usually affect a whole sector, solid-state storage devices tend to produce single-byte errors, making of lzip the perfect format for data stored on such devices.
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.
If you have several copies of a file but all of them are too damaged to repair them (see Repairing files), lziprecover can try to produce a correct file by merging the good parts of the damaged copies.
The merge may succeed even if some copies of the file have all the headers and trailers damaged, as long as there is at least one copy of every header and trailer intact, even if they are in different copies of the file.
The merge will fail if the damaged areas overlap (at least one byte is damaged in all copies), or are adjacent and the boundary can't be determined, or if the copies have too many damaged areas.
All the copies to be merged must have the same size. If any of them is larger or smaller than it should, either because it has been truncated or because it got some garbage data appended at the end, it can be brought to the correct size with the following command before merging it with the other copies:
ddrescue -s<correct_size> -x<correct_size> file.lz correct_size_file.lz
To give you an idea of its possibilities, when merging two copies, each of them with one damaged area affecting 1 percent of the copy, the probability of obtaining a correct file is about 98 percent. With three such copies the probability rises to 99.97 percent. For large files (a few MB) with small errors (one sector damaged per copy), the probability approaches 100 percent even with only two copies. (Supposing that the errors are randomly located inside each copy).
Some types of solid-state device (NAND flash, for example) can produce bursts of scattered single-bit errors. Lziprecover is able to merge files with thousands of such scattered errors by grouping the errors into clusters and then merging the files as if each cluster were a single error.
Here is a real case of successful merging. Two copies of the file 'icecat-3.5.3-x86.tar.lz' (compressed size 9 MB) became corrupt while stored on the same NAND flash device. One of the copies had 76 single-bit errors scattered in an area of 1020 bytes, and the other had 3028 such errors in an area of 31729 bytes. Lziprecover produced a correct file, identical to the original, in just 5 seconds:
$ lziprecover -vvm a/icecat-3.5.3-x86.tar.lz b/icecat-3.5.3-x86.tar.lz Merging member 1 of 1 (2552 errors) 2552 errors have been grouped in 16 clusters. Trying variation 2 of 2, block 2 Input files merged successfully.
Note that the number of errors reported by lziprecover (2552) is lower than the number of corrupt bytes (3104) because contiguous corrupt bytes are counted as a single multibyte error.
The name of the fixed file produced by '--merge' and '--repair' is made by appending the string '_fixed.lz' to the original file name. If the original file name ends with one of the extensions '.tar.lz', '.lz' or '.tlz', the string '_fixed' is inserted before the extension.
Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away.
-- Antoine de Saint-Exupery
In the diagram below, a box like this:
+---+ | | <-- the vertical bars might be missing +---+
represents one byte; a box like this:
+==============+ | | +==============+
represents a variable number of bytes.
A lzip file consists of a series of "members" (compressed data sets). The members simply appear one after another in the file, with no additional information before, between, or after them.
Each member has the following structure:
+--+--+--+--+----+----+=============+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ID string | VN | DS | LZMA stream | CRC32 | Data size | Member size | +--+--+--+--+----+----+=============+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
All multibyte values are stored in little endian order.
Sometimes extra data are found appended to a lzip file after the last member. Such trailing data may be:
Trailing data are in no way part of the lzip file format, but tools reading lzip files are expected to behave as correctly and usefully as possible in the presence of trailing data.
Trailing data can be safely ignored in most cases. In some cases, like that of user-added data, they are expected to be ignored. In those cases where a file containing trailing data must be rejected, the option '--trailing-error' can be used. See --trailing-error.
Lziprecover facilitates the management of metadata stored as trailing data in lzip files. See the following examples:
Example 1: Add a comment or description to a compressed file.
# First append the comment as trailng data to a lzip file echo 'This file contains this and that' >> file.lz # This command prints the comment to standard output lziprecover --dump-tdata file.lz # This command outputs file.lz without the comment lziprecover --strip-tdata file.lz # This command removes the comment from file.lz lziprecover --remove-tdata file.lz
Example 2: Add and verify a cryptographically secure hash. (This may be convenient, but a separate copy of the hash must be kept in a safe place to guarantee that both file and hash have not been maliciously replaced).
sha256sum < file.lz >> file.lz lziprecover --strip-tdata file.lz | sha256sum -c \ <(lziprecover --dump-tdata file.lz)
Example 1: Restore a regular file from its compressed version 'file.lz'. If the operation is successful, 'file.lz' is removed.
lziprecover -d file.lz
Example 2: Verify the integrity of the compressed file 'file.lz' and show status.
lziprecover -tv file.lz
Example 3: The right way of concatenating the decompressed output of two or more compressed files. See Trailing data.
Don't do this cat file1.lz file2.lz file3.lz | lziprecover -d Do this instead lziprecover -cd file1.lz file2.lz file3.lz
Example 4: Decompress 'file.lz' partially until 10 KiB of decompressed data are produced.
lziprecover -D 0,10KiB file.lz
Example 5: Decompress 'file.lz' partially from decompressed byte 10000 to decompressed byte 15000 (5000 bytes are produced).
lziprecover -D 10000-15000 file.lz
Example 6: Repair small errors in the file 'file.lz'. (Indented lines are abridged diagnostic messages from lziprecover).
lziprecover -v -R file.lz Copy of input file repaired successfully. lziprecover -tv file_fixed.lz file_fixed.lz: ok mv file_fixed.lz file.lz
Example 7: Split the multimember file 'file.lz' and write each member in its own 'recXXXfile.lz' file. Then use 'lziprecover -t' to test the integrity of the resulting files.
lziprecover -s file.lz lziprecover -tv rec*file.lz
Example 8: Recover a compressed backup from two copies on CD-ROM with error-checked merging of copies. (See the ddrescue manual for details about ddrescue).
ddrescue -d -r1 -b2048 /dev/cdrom cdimage1 mapfile1 mount -t iso9660 -o loop,ro cdimage1 /mnt/cdimage cp /mnt/cdimage/backup.tar.lz rescued1.tar.lz umount /mnt/cdimage (insert second copy in the CD drive) ddrescue -d -r1 -b2048 /dev/cdrom cdimage2 mapfile2 mount -t iso9660 -o loop,ro cdimage2 /mnt/cdimage cp /mnt/cdimage/backup.tar.lz rescued2.tar.lz umount /mnt/cdimage lziprecover -m -v -o backup.tar.lz rescued1.tar.lz rescued2.tar.lz Input files merged successfully. lziprecover -tv backup.tar.lz backup.tar.lz: ok
Example 9: Recover the first volume of those created with the command 'lzip -b 32MiB -S 650MB big_db' from two copies, 'big_db1_00001.lz' and 'big_db2_00001.lz', with member 07 damaged in the first copy, member 18 damaged in the second copy, and member 12 damaged in both copies. The correct file produced is saved in 'big_db_00001.lz'.
lziprecover -m -v -o big_db_00001.lz big_db1_00001.lz big_db2_00001.lz Input files merged successfully. lziprecover -tv big_db_00001.lz big_db_00001.lz: ok
The lziprecover package also includes unzcrash, a program written to test robustness to decompression of corrupted data, inspired by unzcrash.c from Julian Seward's bzip2. Type 'make unzcrash' in the lziprecover source directory to build it.
By default, unzcrash reads the specified file and then repeatedly decompresses it, increasing 256 times each byte of the compressed data, so as to test all possible one-byte errors. Note that it may take years or even centuries to test all possible one-byte errors in a large file (tens of MB).
--block option is given, unzcrash reads the specified file
and then repeatedly decompresses it, setting all bytes in each
successive block to the value given, so as to test all possible full
--truncate option is given, unzcrash reads the specified
file and then repeatedly decompresses it, truncating the file to
increasing lengths, so as to test all possible truncation points.
None of the three test modes described above should cause any invalid memory accesses. If any of them does, please, report it as a bug to the maintainers of the decompressor being tested.
Unzcrash really executes as a subprocess the shell command specified in the first non-option argument, and then writes the file specified in the second non-option argument to the standard input of the subprocess, modifying the corresponding byte each time. Therefore unzcrash can be used to test any decompressor (not only lzip), or even other decoder programs having a suitable command line syntax.
If the decompressor returns with zero status, unzcrash compares the output of the decompressor for the original and corrupt files. If the outputs differ, it means that the decompressor returned a false negative; it failed to recognize the corruption and produced garbage output. The only exception is when a multimember file is truncated just after the last byte of a member, producing a shorter but valid compressed file. Except in this latter case, please, report any false negative as a bug.
In order to compare the outputs, unzcrash needs a 'zcmp' program able to understand the format being tested. For example the one provided by 'zutils'. See zcmp
The format for running unzcrash is:
unzcrash [options] "lzip -tv" filename.lz
Unzcrash supports the following options:
|Examples of range||Tests errors of N-bit
|1,2,3||1, 2 and 3
|2-4||2, 3 and 4
|1,3-5,8||1, 3, 4, 5 and 8
|1-3,5-8||1, 2, 3, 5, 6, 7 and 8
--positionto end of file). Negative values are relative to the rest of the file.
--zcmp=falseto disable comparisons.
Exit status: 0 for a normal exit, 1 for environmental problems (file not found, invalid flags, I/O errors, etc), 2 to indicate a corrupt or invalid input file, 3 for an internal consistency error (eg, bug) which caused unzcrash to panic.
There are probably bugs in lziprecover. There are certainly errors and omissions in this manual. If you report them, they will get fixed. If you don't, no one will ever know about them and they will remain unfixed for all eternity, if not longer.
If you find a bug in lziprecover, please send electronic mail to
firstname.lastname@example.org. Include the version number, which you can
find by running