Tebibyte to Exabit

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.

One exabit = 10¹⁸ bits = 125,000 terabytes = 125 petabytes. If every person on Earth (8 billion people) each stored 15 GB of data — roughly a modern smartphone's photos and messages — the total would be about 120 exabytes, or about 960 exabits. The entire human genome is about 1.5 GB; sequencing every person on Earth would produce about 12 exabytes of data.

Cisco's annual internet traffic reports estimated global IP traffic at roughly 4.8 exabytes per day in 2022, rising about 20% per year. Expressed in bits, that's about 38 exabits per day or roughly 440 petabits per second continuously. Video streaming accounts for over 60% of total internet traffic volume.

Data gravity is the principle that massive datasets attract applications, services, and additional data toward them — rather than being moved to where processing occurs. At exabit scale, physically transferring data becomes impractical: moving 1 exabit over a 100 Gbps link takes 116 days. Instead, companies deploy compute resources alongside the data. This effect drives cloud concentration — once an organisation stores exabits in AWS or Azure, the cost and latency of moving that data elsewhere creates powerful vendor lock-in, shaping the economics of the entire cloud industry.

The Square Kilometer Array (SKA), under construction in Australia and South Africa, will be the world's largest radio telescope. Its thousands of antennas will collectively produce roughly 1 exabit of raw sensor data per day — more than the entire global internet traffic of the early 2000s. This data cannot be stored in full; instead, on-site supercomputers reduce it by a factor of ~10,000 in real time, keeping only scientifically relevant signals. The SKA illustrates how radio astronomy pushes data processing to extreme scales that rival commercial internet infrastructure.

At 1 Gbps (a fast home connection), downloading 1 exabit would take 1 billion seconds — about 31.7 years. At 1 Tbps (a high-end data center link), it would take 1 million seconds, or about 11.6 days. This illustrates why exabit-scale data movements require massively parallel infrastructure — no single link or device handles exabit transfers directly.