Tebibyte to Gibibit

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 gigabit (Gbit) = 10⁹ bits = 1,000,000,000 bits (SI). A gibibit (Gibit) = 2³⁰ bits = 1,073,741,824 bits (IEC binary). The difference is 7.37%. Consumer networking equipment and ISP speed ratings use decimal gigabits; memory and chip designers sometimes use gibibits when binary precision is required.

Virtually all networking equipment — routers, switches, NICs, ISP speed ratings — uses decimal gigabits (Gbit). A "1 Gbps" (gigabit per second) connection means exactly 1,000,000,000 bits per second, not 1,073,741,824 bits per second. Network standards (Ethernet IEEE 802.3) are defined in SI units.

DDR memory bandwidth is calculated from clock speed, bus width, and transfers per clock. A DDR5-4800 module on a 64-bit bus delivers 4,800 MT/s × 64 bits = 307,200 Mbit/s ≈ 292.97 Gibit/s. Engineers use gibibits when verifying that memory throughput matches binary-aligned cache line sizes (typically 512 bits = 64 bytes), ensuring no fractional transfers occur during burst reads.

GPU memory bandwidth is typically quoted in gigabytes per second (GB/s) using SI decimal values — not gibibits. For example, NVIDIA's RTX 4090 has 1,008 GB/s of memory bandwidth (decimal). Some academic papers and IEEE publications convert this to GiB/s or Gibit/s for precision, but consumer GPU marketing universally uses SI decimal units.

Gibibit appears in: IEEE standards documents specifying memory interface speeds, JEDEC memory specifications, some academic networking papers, and storage controller datasheets. Consumer-facing software, marketing materials, and OS interfaces virtually never display gibibits — they show gigabits (networking) or gigabytes (storage). It is primarily a precision engineering unit.