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…
- Of Chips and Acquisitions | Gestalt IT Rundown: August 21, 2019 - August 21, 2019
- Kubernetes Is Evolving Into an Enterprise-Friendly Platform, but Challenges Remain - August 16, 2019
- Going Independent - August 15, 2019
- AMD Wasn’t Built In A Day | Gestalt IT Rundown: August 14, 2019 - August 14, 2019
- SaaS Backup Isn’t My Problem – The On-Premise IT Roundtable - August 13, 2019
- Jira and the Definition of All | Gestalt IT Rundown: August 7, 2019 - August 7, 2019
- What’s In Your Bucket | Gestalt IT Rundown: July 31, 2019 - July 31, 2019
- VPNemy at the Gates | Gestalt IT Rundown: July 24, 2019 - July 24, 2019
- Germany Drops the Hesse on Microsoft | Gestalt IT Rundown: July 17, 2019 - July 17, 2019
- FUD: Fear, UK, and DNS | Gestalt IT Rundown: July 10, 2019 - July 10, 2019