Skip to content
Novus Examples
tar10 KB

TAR - Padded to a 10240-Byte Record

The same three members followed by the end-of-archive blocks and then zero padding out to a whole 10240-byte record - tar's historical blocking factor of 20, still the default. The archive is 10240 bytes for 616 bytes of content, which is what makes tiny tarballs look so wasteful before compression.

Archive contents — 3 entriestar
  • README.txt
  • app.log
  • app.1.log

Specifications

Seed
20260807
Members
3
Block Size
512
Blocking Factor
20
Record Bytes
10240
File Bytes
10240
Trailing Zero Bytes
6144
Why
tar's historical default writes whole tape records, not whole blocks

Testing contract

Expected to pass
Scenario
Extract every member and compare the file size against the sum of the member sizes.
Expected result
All 3 members extract intact, the file is exactly 10240 bytes - a whole multiple of 10240 - and the padding after the end-of-archive blocks is all zeros.

What is a .tar file?

TAR (Tape Archive) is a Unix archive format that concatenates files with their metadata into a single uncompressed stream of fixed-size blocks. It preserves permissions, ownership, and directory structure but applies no compression itself. It is usually paired with a compressor such as gzip or xz.

How to use this file

Use an example TAR to test archive extraction, metadata and permission preservation, streaming block parsing, and pipelines that combine tar with external compression.

How to use this file for testing

“TAR - Padded to a 10240-Byte Record” is a deterministic Novus Examples fixture for Conversion testing, Performance 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 record-padded.tar       # list
tar -xf record-padded.tar -C out/  # extract

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