Up until reading this post by Justin Parisi, I’ll admit I was always a little confused when I saw people write GiB instead of GB. I think I rationalized it as a stylized choice, people trying to be a little extra cute in their writing. Or perhaps it had something to do with the context of presenting that number. Forgive my ignorance, but I didn’t think they were a totally separate measure.
Really what this signifies is a significant difference in how storage is measured, binary vs decimal. Obviously I’m not the only one confused. NetApp recently fixed a bug in ONTAP that displayed binary storage figures with a decimal description.
As Justin points out, make sure you look at what a storage company is actually representing in their capacity figures. Assuming decimal, even if more common, could leave you with significantly less if you’re wrong.
Justin Parisi comments:
What happens when you use decimal vs. binary to measure storage? Well, it can mean that what you thought was 316GB of storage is really only 288GiB – depending on how the vendor has decided to display it.
Read more at: ALL YOUR BASE…
- You’re Wrong About Data Protection Policy – The On-Premise IT Roundtable - May 14, 2019
- Gestalt News for the Week of May 13, 2019 - May 13, 2019
- The Perpetual Plugin Problem | Gestalt IT Rundown: May 8, 2019 - May 8, 2019
- Gestalt News for the Week of May 6 ,2019 - May 6, 2019
- Azure and VMware Team Up | Gestalt IT Rundown: May 1, 2019 - May 1, 2019
- Bringing Yourself to Work – The On-Premise IT Roundtable - April 30, 2019
- Gestalt News for the Week of April 29, 2019 - April 29, 2019
- Docker Partners With Arm | Gestalt IT Rundown: April 24, 2019 - April 24, 2019
- Gestalt News for the Week of April 22, 2019 - April 22, 2019
- Patent Peace in Our Time | Gestalt IT Rundown: April 17, 2019 - April 17, 2019