LZIPRECOVER(1)

πŸ“¦
version 1.26 Β· 4 versions
, in ubuntu resolute, ubuntu stonking

πŸ’– lziprecover β€” the manual, but make it cute πŸ’–

okay bestie, welcome to lziprecover(1), a User Commands moment, and honestly? she's giving lifesaver. no cap. 🫢


✨ NAME ✨

lziprecover β€” recovers data from damaged files πŸ©ΉπŸ’Ύ


πŸ¦‹ SYNOPSIS πŸ¦‹

lziprecover [options] [files]

🌸 DESCRIPTION 🌸

So. Lziprecover is a data recovery tool and a decompressor for files in the lzip compressed data format (.lz). Two jobs, both iconic. πŸ’…

She also provides Forward Error Correction files (.fec) that can be used to repair any kind of file, not only lzip files. A fec file can be used as a recovery record for a tar.lz archive. yes queen, insurance policy energy. πŸ›‘οΈβœ¨

Lziprecover can remove the damaged members from multimember files β€” for example multimember tar.lz archives. bye damaged bits, you will not be missed. πŸ’€

And she provides random access to the data in multimember files; she only decompresses the members containing the desired data. efficient. main character. not doing extra work for nobody. πŸ‘‘


✨ OPTIONS ✨

  • -h, --help β€” display this help and exit. the "bestie explain" button πŸ₯Ί
  • -V, --version β€” output version information and exit. she'll tell you who she is πŸ’β€β™€οΈ
  • -a, --trailing-error β€” exit with error status if trailing data. no loose ends tolerated 🚫
  • -A, --alone-to-lz β€” convert lzma-alone files to lzip format. glow-up conversion ✨
  • -b, --block-size=<bytes> β€” make FEC block size a multiple of <bytes>. math but make it tidy πŸ“
  • -B, --byte-repair β€” try to repair a corrupt byte in file. one little byte, one big rescue 🩹
  • -c, --stdout β€” write to standard output, keep input files. show me everything, keep the originals πŸ’–
  • -d, --decompress β€” decompress, test compressed file integrity. the classic πŸŽ€
  • -D, --range-decompress=<n-m> β€” decompress a range of bytes to stdout. just the slice you asked for 🍰
  • -e, --reproduce β€” try to reproduce a zeroed sector in file. forensic girly πŸ”
  • --lzip-level=N|a|m[N] β€” reproduce one level, all, or match length
  • --lzip-name=<name> β€” name of lzip executable for --reproduce
  • --reference-file=<file> β€” reference file for --reproduce
  • -f, --force β€” overwrite existing output files. she's not asking permission 😀
  • -F, --fec=c[N]|r|t|l β€” create, repair, test, list (using) fec file
  • -0 .. -9 β€” set FEC fragmentation level [default 9]
  • --fec-file=<file>[/] β€” read fec file from <file> or directory
  • -i, --ignore-errors β€” ignore non-fatal errors. not today, drama πŸ™ˆ
  • -k, --keep β€” keep (don't delete) input files. she's a keeper fr fr πŸ’œ
  • -l, --list β€” print (un)compressed file sizes. receipts, basically 🧾
  • -m, --merge β€” repair errors in file using several copies. teamwork makes the dream work 🀝
  • -n, --threads=<n> β€” set number of threads for fec create [2]. more threads, more slay 🧡
  • -o, --output=<file>[/] β€” place the output into <file> or directory
  • -q, --quiet β€” suppress all messages. shhh, she's working 🀫
  • -r, --recursive β€” (fec) operate recursively on directories. down the rabbit hole πŸ‡
  • -R, --dereference-recursive β€” (fec) recursively follow symbolic links. following the vibes wherever they go πŸ”—
  • -s, --split β€” split multimember file in single-member files. divide and conquer βœ‚οΈ
  • -t, --test β€” test compressed file integrity. vibe check, but for files βœ…
  • -v, --verbose β€” be verbose (a 2nd -v gives more). she will tell you everything πŸ—£οΈ
  • --append=<file> β€” append <file> as trailing data
  • --dump=<list>:d:e:t β€” dump members, damaged, empty, tdata to stdout
  • --remove=<list>:d:e:t β€” remove members, tdata from files in place
  • --strip=<list>:d:e:t β€” copy files to stdout stripping members given
  • --loose-trailing β€” allow trailing data seeming corrupt header
  • --nonzero-repair β€” repair in place a nonzero first LZMA byte

If no file names are given, or if a file is '-', lziprecover decompresses from standard input to standard output. 🫢

Numbers may contain underscore separators between groups of digits and may be followed by a SI or binary multiplier: 1_234_567kB, 4KiB. cute and legible, we love that for us.

The argument to --fec=create may be a number of blocks (-Fc20), a percentage (-Fc5%), or a size in bytes (-Fc10KiB). pick your fighter πŸ₯Š

To extract all the files from archive foo.tar.lz, use the commands:

tar -xf foo.tar.lz

or

lziprecover -cd foo.tar.lz | tar -xf -

(pipe queen behavior honestly 🫢✨)


πŸ’€ EXIT STATUS πŸ’€

  • 0 β€” for a normal exit. we ate and left no crumbs 😌
  • 1 β€” for environmental problems (file not found, invalid command-line options, I/O errors, etc). it's not her, it's the environment 😭
  • 2 β€” to indicate a corrupt or invalid input file. that file is not okay πŸ’…
  • 3 β€” for an internal consistency error (e.g., bug) which caused lziprecover to panic. she's screaming, and validly so 🚨

πŸ› REPORTING BUGS πŸ›

Found a bug? tell the devs, bestie, they wanna know:

Report bugs to lzip-bug@nongnu.org

Lziprecover home page: http://www.nongnu.org/lzip/lziprecover.html


Copyright Β© 2026 Antonio Diaz Diaz. License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html>

This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. (yes the all-caps is theirs, it's giving legal drama πŸ“’)


πŸ‘€ SEE ALSO πŸ‘€

The full documentation for lziprecover is maintained as a Texinfo manual. If the info and lziprecover programs are properly installed at your site, the command

info lziprecover

should give you access to the complete manual. iykyk πŸ“–βœ¨


and that's the whole page, bestie!! this is lziprecover 1.26, born February 2026, and she's still serving User Commands realness. mwah. πŸ’‹πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from