Tebibyte to Tebibit

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.

A terabit (Tbit) = 10¹² bits (SI decimal). A tebibit (Tibit) = 2⁴⁰ bits = 1,099,511,627,776 bits (IEC binary). Tebibit is 9.95% larger. At enterprise storage scale, this 10% difference has real financial consequences: a storage specification error confusing Tbit with Tibit on a 100-unit deployment results in nearly 10 units' worth of capacity discrepancy.

Tebibits appear in: NAND flash memory die specifications and yield calculations, high-speed fabric interconnect specifications (InfiniBand HDR = 200 Gbit/s), supercomputer storage system designs, and academic papers on distributed storage systems. Consumer applications never display tebibits; the term is confined to engineering and procurement contexts.

Modern 3D NAND stacks 100+ layers of memory cells vertically. A single die from a 232-layer TLC NAND chip can hold about 1 Tibit (128 GiB) raw capacity. Manufacturers measure at the die level in tebibits because binary addressing maps directly to the physical array geometry — each layer, block, and page aligns to powers of 2. A 16-die package thus holds 16 Tibit (2 TiB) before error correction overhead.

Each binary prefix multiplies by 1,024 instead of 1,000. The compounding effect: kibi vs kilo = 2.4% difference, mebi vs mega = 4.9%, gibi vs giga = 7.4%, tebi vs tera = 9.95%, pebi vs peta = 12.6%, exbi vs exa = 15.3%. The difference grows by approximately 2.4% with each prefix step, making precision in naming increasingly important at larger scales.

1 Tibit = 2⁴⁰ bits = 2⁴⁰ / 8 bytes = 2³⁷ bytes = 137,438,953,472 bytes ≈ 137.4 GB (decimal). To convert Tibit to GB: multiply by 137.4. To convert Tibit to GiB: divide by 8 (since 1 Tibit = 0.125 TiB = 128 GiB). The exact value: 1 Tibit = 128 GiB.