Exbibit to Tebibyte

An exabit (Ebit) = 10¹⁸ bits (SI decimal). An exbibit (Eibit) = 2⁶⁰ bits ≈ 1.1529 × 10¹⁸ bits (IEC binary). Exbibit is 15.29% larger — the cumulative product of using 1,024 instead of 1,000 at each of six prefix steps. This is the largest practically relevant SI vs IEC gap for bit units in current storage contexts.

Exbibit is used in: computer science academic literature on exascale computing, theoretical storage system design papers, and formal IEC/IEEE standards. No commercial product, OS, or consumer application currently displays exbibits. It is primarily a unit for academic and standards consistency — ensuring the IEC prefix family extends uniformly from kibi- to exbi- (and beyond to zebi- and yobi-).

After exbibit (Eibit, 2⁶⁰ bits) come: zebibit (Zibit, 2⁷⁰ bits) and yobibit (Yibit, 2⁸⁰ bits). These are defined in the IEC 80000-13 standard but have no current practical applications. The IEC binary prefix family deliberately mirrors the SI prefix family, ensuring consistent naming as computing scale continues to grow.

Frontier (Oak Ridge, 2022) achieved 1.194 exaFLOPS, with its Slingshot-11 fabric moving data at aggregate rates measurable in exbibits per second across 9,408 nodes. Aurora (Argonne, 2024) targets similar throughput with over 63,000 GPUs. At these scales, a single checkpoint of a full-system simulation can exceed 1 Eibit of state data, making exbibit a natural unit for describing I/O bandwidth requirements.

The IEC currently defines up to yobibit (Yibit, 2⁸⁰ bits). In 2022, the SI system added ronna- (10²⁷) and quetta- (10³⁰), but the IEC has not yet created matching binary prefixes (ronnibit? quettibit?). With global data creation projected to exceed 1 yottabit annually by the 2030s, pressure is mounting for the IEC to extend the binary prefix family — though the naming convention ("ronnibi-"?) remains an open question.

TB (terabyte) = 10¹² bytes = 1,000,000,000,000 bytes (SI decimal). TiB (tebibyte) = 2⁴⁰ bytes = 1,099,511,627,776 bytes (IEC binary). TiB is 9.95% larger. The practical consequence: a 1 TB hard drive (decimal) holds 0.9095 TiB. This 10% gap is the primary reason drive capacity appears lower in the OS than on the box.

ZFS and Btrfs are copy-on-write filesystems designed for TiB-scale pools with built-in features that traditional filesystems lack. ZFS supports inline deduplication — a 10 TiB pool with 40% duplicate data might show 6 TiB of logical usage but only consume 3.6 TiB physically. Btrfs offers transparent compression (zstd), where a 4 TiB dataset of compressible log files might occupy only 1–2 TiB on disk. Both support snapshots that initially consume zero extra space, growing only as data diverges. These features make "used space in TiB" surprisingly complex to report accurately.

Yes. Linux tools (df -h, lsblk) display storage in IEC binary units: KiB, MiB, GiB, TiB. df -h output showing "1.8T" for a 2 TB drive is reporting 1.8 TiB. Modern Linux distributions correctly label these as TiB in technical contexts. This is one of the areas where Linux is more technically precise than Windows or consumer storage labels.

RAID arrays lose capacity to redundancy: RAID 1 mirrors two drives (50% efficiency); RAID 5 loses one drive worth of capacity; RAID 6 loses two drives. A 4-drive RAID 5 array of 2 TB drives has 3 × 2 TB = 6 TB raw usable (decimal), ≈ 5.46 TiB, minus filesystem overhead. Enterprise storage also reserves space for spares, snapshots, and wear levelling, further reducing usable TiB.

No. A tebibyte (TiB) = 2⁴⁰ bytes = 1,099,511,627,776 bytes — about 1.1 trillion bytes. Exactly one trillion bytes = 10¹² bytes = 1 terabyte (TB, decimal). The tebibyte is approximately 10% larger than a trillion bytes. "Terabyte" is often casually used to mean "1 trillion bytes"; "tebibyte" is the precise binary equivalent at 1,024 gibibytes.