{"id":713,"date":"2020-07-05T07:25:59","date_gmt":"2020-07-05T05:25:59","guid":{"rendered":"http:\/\/blog.open-e.com\/?p=713"},"modified":"2025-06-20T09:01:31","modified_gmt":"2025-06-20T09:01:31","slug":"formatted-capacity-confusion-clarified","status":"publish","type":"post","link":"https:\/\/www.open-e.com\/blog\/formatted-capacity-confusion-clarified\/","title":{"rendered":"Binary Powers or Formatted Capacity Confusion"},"content":{"rendered":"

\t\t\t\tLast update: July 05, 2021<\/strong><\/p>\n

From time to time, some meticulous customer asks us how come a fresh formatted hard disk or RAID array volume is smaller than the nominal capacity.\u00a0 For example, when you format a 1TB hard disk, the resulting drive appears to have 931 GB even though the hard disk label claims 1000GB.<\/p>\n

Where are the \u201cmissing\u201d gigabytes?<\/h3>\n

The problem is much more pronounced if someone formats a 16TB RAID volume and, instead of the expected 16000 GB, they only see 14896GB. This looks like a significant loss: 1104 GB. \u201cWe paid for 16000GB!\u201d exclaimed one company controller.<\/p>\n

This phenomenon arises because hard-disk manufacturers and RAID<\/a> array controllers count the capacity differently than the file system does. The prefixes kilo, mega, giga, and tera are used to state powers of ten. However, the data being handled in computer software is typically organized based on powers of 2, so it became customary to call 2**10 a kilobyte, which was really 1024 bytes, not exactly 1000.<\/p>\n

Storage hardware is using the base-ten 10 numeral system<\/strong> capacity units, while the software – the base-two numeral system<\/strong>. So no storage is actually lost, and it is just a question of how the information is represented.<\/span><\/p>\n

IEC System of Prefixes<\/h3>\n

The IEC has created a system of prefixes<\/a> to differentiate between the base 10 and the base 2 systems. In base 2, the proper terms are kibibyte, mebibyte, gibibyte, and tebibyte. The \u201c-bi-\u201d refers to binary<\/strong>. In short, they are KiB, MiB, GiB, TiB. But these are not frequently used.<\/p>\n

However, in order to get exact proof, we have to know the math behind it.<\/p>\n

How to Calculate the Binary Factors?<\/h3>\n

Hard disk manufacturers assume:\u00a0\u00a0 Kilo = 10 3<\/sup> = 1000 (kB)<\/p>\n

File system assumes:\u00a0\u00a0 Kilo = 2 10<\/sup> = 1024 (KiB)<\/p>\n

Let us calculate kB, MB, and GB to KiB, MiB and GiB factors:<\/p>\n

kB – KiB:\u00a0 1000 \/ 1024\u00a0 = 0.977<\/p>\n

MB – MiB:\u00a0 (1000 * 1000)\u00a0 \/\u00a0 (1024 * 1024)\u00a0 = 0.954<\/p>\n

GB – GiB:\u00a0 (1000 * 1000 * 1000)\u00a0 \/\u00a0 (1024 * 1024 * 1024)\u00a0 = 0.931<\/strong><\/p>\n

Now we can easy find out formatted capacity for 1TB hard disk or 16TB (16000GB) array:<\/strong><\/p>\n

1000GB * 0.931 = 931GiB<\/p>\n

16000GB * 0.931 = 14896GiB<\/p>\n

Typically software will display GB as the storage unit size, but actually, it is GiB. Until this is changed, there will always be this confusion about the exact size of storage devices.\t\t<\/p>\n","protected":false},"excerpt":{"rendered":"

Last update: July 05, 2021 From time to time, some meticulous customer asks us how come a fresh formatted hard disk or RAID array volume is smaller than the nominal …<\/p>\n","protected":false},"author":2,"featured_media":55751,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[28],"tags":[116,293],"class_list":["post-713","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-raid","tag-capacity","tag-hard-disk"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/posts\/713","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/comments?post=713"}],"version-history":[{"count":1,"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/posts\/713\/revisions"}],"predecessor-version":[{"id":55752,"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/posts\/713\/revisions\/55752"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/media\/55751"}],"wp:attachment":[{"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/media?parent=713"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/categories?post=713"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/tags?post=713"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}