Skip to content
Novus Examples
tbz242 B

TBZ2 - Empty Archive

The empty tar under bzip2. Its payload is 1024 identical bytes, which is the run-length case bzip2's block sorter treats specially, so this doubles as the smallest sane bzip2 stream to test a decoder against.

Preview — schema + first 5 rowstbz2
structurestringvaluestring
containerTAR + bzip2
members0
compressed size42 bytes
uncompressed size1024 bytes
end-of-archive blocks2 x 512 bytes of zeros
This archive has no members to list; the table describes the container bytes instead.

Specifications

Seed
20260807
Members
0
File Bytes
42
Uncompressed Bytes
1024
Codec
bzip2
Note
bzip2 of 1024 zero bytes - a run-length case its block sorter handles specially

Testing contract

Expected to pass
Scenario
Decompress the bzip2 stream, then list the tar inside it.
Expected result
The bzip2 layer decodes its single run-length block to exactly 1024 bytes of zeros and the tar listing reports 0 members with no error.

What is a .tbz2 file?

TBZ2 is a shorthand extension for a TAR archive compressed with bzip2, equivalent to .tar.bz2. The tar step bundles files and metadata, then bzip2 compresses the combined stream for a higher ratio. It is used for distributing larger source and data archives.

How to use this file

Use an example TBZ2 to test the decompress-then-untar pipeline with bzip2, and tools that recognize the abbreviated .tbz2 extension.

How to use this file for testing

“TBZ2 - Empty Archive” is a deterministic Novus Examples fixture for Conversion testing, Error handling, Compression testing. The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.

Documented properties for this file: seed 20260807. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Archive fixtures are documented down to their member list (shown on this page) and are deliberately safe — no zip bombs, executables, or hidden payloads. Test extractors against nested, unicode, empty, and encrypted variants.

Code examples

tar -tf empty.tbz2       # list
tar -xf empty.tbz2 -C out/  # extract

Generated by generation/archives_p7.py. Free for any use, no attribution required — license.