Tebibyte to Block
TiB
blk
Conversion History
| Conversion | Reuse | Delete |
|---|---|---|
| No conversion history to show. | ||
Quick Reference Table (Tebibyte to Block)
| Tebibyte (TiB) | Block (blk) |
|---|---|
| 0.5 | 4,398,046,511,104 |
| 1 | 8,796,093,022,208 |
| 2 | 17,592,186,044,416 |
| 4 | 35,184,372,088,832 |
| 8 | 70,368,744,177,664 |
| 16 | 140,737,488,355,328 |
| 20 | 175,921,860,444,160 |
About Tebibyte (TiB)
A tebibyte (TiB) equals exactly 1,099,511,627,776 bytes (2⁴⁰ bytes) in the IEC binary system. It is 9.95% larger than the decimal terabyte (10¹² bytes). The tebibyte is used for large storage volumes: enterprise SAN (storage area network) arrays, RAID configurations, and NAS devices often display capacity in TiB. A drive labelled "1 TB" by its manufacturer contains approximately 0.909 TiB. The ~10% gap at this scale is significant for data center capacity planning — a server room specified in TB vs TiB could be off by 10% of the total procurement budget.
A 4 TB NAS drive holds approximately 3.64 TiB. Enterprise SAN systems are commonly sized in multiples of TiB.
About Block (blk)
A block (also called a disk block or storage block) is a fixed-size unit of data used by filesystems and storage devices when reading or writing to disk. Block size is not fixed across systems — common sizes are 512 bytes (the historic disk sector size), 4,096 bytes (4 KiB, the modern standard for HDDs and SSDs), and larger sizes (64 KiB, 1 MiB) for enterprise storage arrays. Filesystems allocate space in whole blocks: a 1-byte file still consumes one full block on disk. Block size affects performance (larger blocks favor sequential reads) and space efficiency (smaller blocks waste less space on small files).
A 4,096-byte (4 KiB) block filesystem storing a 1-byte text file uses 4,096 bytes of disk space — 4,095 bytes are wasted. On a system with 1 million tiny files, this slack space becomes significant.
Tebibyte – Frequently Asked Questions
What is the difference between TB and TiB?
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.
How do modern filesystems like ZFS and Btrfs handle TiB-scale storage?
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.
Does Linux use TiB for storage?
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.
How does RAID affect usable TiB?
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.
Is a tebibyte the same as a trillion bytes?
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.
Block – Frequently Asked Questions
What is the default block size for modern hard drives and SSDs?
Modern hard drives (2011+) and SSDs use 4,096-byte (4 KiB) physical sectors — known as "Advanced Format" or AF. Legacy drives used 512-byte sectors. Filesystems (NTFS, ext4, APFS) typically use 4 KiB logical block sizes to match physical sectors, which avoids the performance penalty of misaligned writes. Enterprise SSDs may use larger block sizes (16 KiB or more) for better parallelism.
What is block size in cloud storage?
Cloud block storage services (AWS EBS, Azure Managed Disks, GCP Persistent Disk) use I/O block sizes typically of 4 KiB or 16 KiB. Performance is measured in IOPS (I/O operations per second) and throughput (MB/s) — both depend on block size. A throughput-optimized workload (sequential video) benefits from large blocks; an IOPS-optimized workload (database random reads) uses small blocks.
Why does a tiny file take up so much disk space?
Filesystems allocate disk space in whole blocks. On a system with 4 KiB blocks, every file — no matter how small — occupies at least 4,096 bytes. A directory of 10,000 small configuration files (each 100 bytes of content) uses 40 MB of disk space (10,000 × 4,096 bytes) rather than 1 MB (10,000 × 100 bytes). This is called "block slack" or "internal fragmentation".
What is the difference between a disk block and a database block?
Disk blocks (filesystem blocks) are typically 512 bytes to 4 KiB. Database blocks (database pages) are the unit of I/O for a database engine — typically 8 KiB (PostgreSQL, SQL Server), 16 KiB (MySQL InnoDB), or 32 KiB (Oracle, configurable). Database blocks usually align to multiples of disk blocks for efficiency. Reading one database page may involve reading 2–8 disk blocks.
What is RAID stripe size and how does it relate to block size?
RAID stripe size (or chunk size) is the amount of data written to each drive before moving to the next drive in the array — typically 64 KiB to 512 KiB. It should be set to match your workload: sequential large-file workloads benefit from larger stripe sizes; random small-block workloads benefit from stripe sizes closer to the filesystem block size. Mismatched stripe and block sizes cause write amplification and reduce RAID performance.