Kilobit to Tebibyte

The iconic dial-up handshake screech was a negotiation protocol between two modems. The initial tones tested line quality; the harsh noise burst was both modems rapidly cycling through modulation schemes (V.34, V.90) to find the fastest reliable speed — typically 28.8–56 kb/s. The sounds encoded training sequences, equaliser coefficients, and error-correction parameters, all transmitted as audio tones over a voice telephone line designed for 3.4 kHz bandwidth. The entire handshake lasted 10–30 seconds and transferred only a few kilobits of control data before the connection went silent for actual data transfer.

128 kb/s is considered acceptable quality for casual listening; 192–256 kb/s is a good balance of quality and file size; 320 kb/s is the maximum MP3 bitrate and is near-indistinguishable from lossless for most listeners. At 128 kb/s, one hour of audio is roughly 57 MB; at 320 kb/s, the same hour is about 144 MB.

No. A kilobit (kb) = 1,000 bits (SI, decimal). A kibibit (Kibit) = 1,024 bits (IEC, binary). The difference is small at this scale (2.4%) but compounds into significant gaps at larger prefixes. Network and telecom equipment use decimal kilobits; some older computing hardware documentation may use the binary definition.

The fastest consumer dial-up modems reached 56 kb/s (V.90 / V.92 standard), though practical speeds were often 40–50 kb/s due to line quality. At 56 kb/s, downloading a 5 MB MP3 file took about 12 minutes. By comparison, a modern 100 Mbps broadband connection is roughly 1,800 times faster.

Common audio bitrates: voice calls use 8–64 kb/s (G.711 codec = 64 kb/s); AAC audio at 96–256 kb/s; MP3 at 128–320 kb/s; lossless FLAC at 700–1,400 kb/s depending on audio content. Streaming services like Spotify use 24 kb/s (low) to 320 kb/s (premium) for music delivery.

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.