The OS uses 1024 and the drive manufacturers are using 1000.
Which is why a 1TB drive shows 931GiB of capacity. (1024 GiB =1 TiB, 1024MiB =1 GiB, 1024KiB =1MiB, 1024 Bytes =1KiB) but the drive manufacturers using SI prefixes doing 1000 Bytes =1 KB, 1000 KB = 1MB, 1000MB = 1GB, 1000GB = 1TB.
Thus the discrepancy.
You will never hear me say gibibytes in public though. Telling on my nerdy ass self is for private conversations.
To make things more confusing, there's a goofy formula which tells you the actual capacity of a given advertised capacity. A drive advertised as 1 TB will always have exactly 1,000,204,886,016 bytes. It helps to have consistency, but nobody seems to knows where the formula came from.
Its great when you buy larger capacity drives and start to lose entire terabytes
Bootlickers will then argue it's cool that the manufacturer screws you out of almost a hundred gigs.
The old GiB vs GB
SSDs also have over-provisioning (which is not a bad thing imo)
Has anyone ever used the last byte on any hard disc in a successful manner?
I mean not by just putting a too large file there, but something that actually utilized that final byte and having the machine still run flawlessly?
That's your OS using base 2 units and calling it TB. The drive ships with 1TB.
I really love how this really applied to basically everything, the more you know about Linux for example – the most you are happy that something worked instead of asking HOW it works
I'm talking to you, RAM memory!
Bits sold as bytes.
all 52 comments