Petabyte to Tebibyte

1 petabyte (PB) = 1,000 terabytes (TB) in the SI decimal system. In the binary IEC system, 1 pebibyte (PiB) = 1,024 tebibytes (TiB) = 1,125,899,906,842,624 bytes. The distinction matters for enterprise storage procurement: a petabyte of raw disk capacity appears as about 909 TiB in an OS reporting binary units.

Petabyte-scale storage is common at: social media platforms (Facebook/Meta stores over 100 PB of photos alone), streaming services (Netflix's content library is estimated at 100+ PB), government agencies (US NSA, CERN particle physics data), genomic research institutions, and large financial exchanges storing tick-level trading data. Major cloud providers (AWS, Azure, GCP) collectively store zettabytes.

In 2024, cloud storage costs roughly $20–25 per TB per month (S3 standard tier), making 1 PB approximately $20,000–$25,000/month. Raw enterprise disk hardware for 1 PB runs about $20,000–$50,000 upfront (at $20–50 per TB for high-density drives), plus ongoing power, cooling, and management overhead. Tape-based archival storage is considerably cheaper at $2–5 per TB.

YouTube users upload approximately 500 hours of video per minute, or 720,000 hours per day. At an average compressed size of 1–2 GB per hour of HD video, that equates to roughly 720–1,440 TB (0.7–1.4 PB) of new video data per day — before YouTube re-encodes into multiple formats and quality levels, which multiplies storage requirements several-fold.

The SI prefix hierarchy above petabyte: exabyte (EB, 10¹⁸ bytes), zettabyte (ZB, 10²¹ bytes), yottabyte (YB, 10²⁴ bytes), ronnabyte (RB, 10²⁷ bytes), and quettabyte (QB, 10³⁰ bytes) — the last two added by the BIPM in 2022. Current global data storage is estimated in the hundreds of exabytes; no single organisation approaches yottabyte scale.

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.