A while back I presented a diagram showing how storage is lost throughout the provisioning process.
I’ve added a few more items onto the diagram and heres version 2. The additions show reasons why storage is lost at various points in the cycle, for example, disks not not in use, hot spares, not using all the remaining space on the disk etc.
If anyone has additional reasons I’ve missed, then please let me know.
The next step is to look at ways of retrieving this storage and improving efficiency.
If you enjoyed this article, please consider sharing it!
4 Responses to Storage Waterfall Revisited
Leave a Reply
You must be logged in to post a comment.
Let’s not forget that drive manufacturers state capacity in base 10 terms and storage vendors state them in base 2 terms. To a drive manufacturer, 1GB is 1,000,000,000 bytes; to a storage vendor, 1GB is 1,073,741,824 bytes. That’s about a 7.4% difference right there before we even consider anything else.
John
Great one, thanks! Shame this is one we can’t do anything about.
Amazing! Reminds me of the power consumption “food chain” and how much power is lost before it even gets to PCs, servers and storage systems.
How about comparing contrasting these two waterfalls?
[...] There’s also the issue with how the data should be presented - Storage Waterfall Revisited. [...]