Tebibyte to Bit

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 bit is a single binary value (0 or 1); a byte is a group of 8 bits. Bytes are the standard unit for file sizes, memory, and storage. Network speeds are typically quoted in bits per second (Mbps), while file sizes use bytes (MB) — so a 100 Mbps connection downloads 100 megabits, or about 12.5 megabytes, per second.

Networking hardware physically transmits one bit at a time over a wire or radio signal, so bits per second is the natural unit for measuring throughput. The convention predates widespread file-size awareness. When you see "100 Mbps broadband", your actual download speed in MB/s is about 1/8 of that — roughly 12.5 MB/s.

A classical bit is definitively 0 or 1. A qubit can exist in a superposition of both states simultaneously, described by two complex probability amplitudes. When measured, a qubit collapses to 0 or 1 — yielding one classical bit of information. The power of qubits lies in entanglement and interference during computation, not in storing more data per unit. A 100-qubit quantum computer does not store 100 bits more efficiently; it explores 2¹⁰⁰ computational paths in parallel for specific algorithm types like factoring and search.

Information theory, developed by Claude Shannon in 1948, quantifies how much information a message contains. One bit is the amount of information needed to resolve a choice between two equally likely outcomes. This abstraction underpins all digital compression, encryption, and error-correction — from MP3 audio to HTTPS security.

In practice, modern computers cannot address or store a single bit individually — the minimum addressable unit is one byte (8 bits). Trying to store a single bit requires a full byte, with 7 bits unused. Some specialised hardware and bit-packing algorithms can store multiple boolean values per byte, but standard memory hardware works at byte granularity.