The MSA reports the sizes as marketing sizes (Base 10), but there's an option to change it to Base 2, i.e. the real technical size.
Please take a look at e.g. https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c01762974
That description may not be for for your exact MSA model, but the modification steps should be similar.
André
The MSA reports the sizes as marketing sizes (Base 10), but there's an option to change it to Base 2, i.e. the real technical size.
Please take a look at e.g. https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c01762974
That description may not be for for your exact MSA model, but the modification steps should be similar.
André
What you mean marketing size.
MSA shows right one as that is realy size of disk I've inserted there.
3x1.2TB+800GB=4.4TB
When I did created storage on vSphere it showed 4.090 TB.
Where is 300+ GB?
Where is 300+ GB?
It's in the maths, i.e. the conversion from TB to TiB.
Maybe Units converter - convert TB into TiB can help to explain this better.
Simply enter 4.4 TB TiB into the input filed, and you'll see that you end up with ~4TiB.
Btw. it's the same for the disks that you mentioned. A 1.2TB disk has a capacity of ~1.09TiB.
André
So that means vSphere shows in TiB?
Why then not to write TiB intead of TB.
Confusing things.
So that means vSphere shows in TiB?
Yes, they show the real technical size.
Why then not to write TiB intead of TB.
Sorry, I can't answer this.
It's indeed confusing to have such a distinction anyway. In the early IT times 1kB equaled 1,024 Bytes, and nobody ever thought of 1kB = 1,000 Bytes, or s.th. like TB vs. TiB.
André
as Andre has stated this is the difference between a base 2 (binary) Terabyte and a base 10 (Decimal) Terabyte. The former used by computing systems to denote capacity and the later by Marketing departments to inflate their capacity.
Andre, those were purer times before marketing kidnapped, the technical space with verbal athletics.