• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Crucial m4 exactly 64gb?

tigersty1e

Golden Member
Sort of weird question.

I know the mechanical drives have less than stated amounts. But not sure of this drive. My OCZ agility 60gb drive has exactly 60gb.

Does the M4 have exactly 64gb of usable space?
 
Depending on the manufacturer, they may or may not calculate 1GB as 1 000 000 000 bytes. The best way to find out whether they do this or not would be to look up their eaerlier drives and comments on those.
 
crucial uses 1000*1000 like all other hd/SSD makers that I know of
device size with M = 1024*1024: 122104 MBytes
device size with M = 1000*1000: 128035 MBytes (128 GB)
so my 128GB M4 is ~122GB
the 64GB version should be half that

M4 128GB:
Disk /dev/sda: 128.0 GB, 128035676160 bytes
here is a 1TB caviar for comparison:
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
same metric used
 
Last edited:
I know the mechanical drives have less than stated amounts.

Incorrect. Every mechanical drive that I've seen has slightly more space than the advertised amount. You just have to remember that they advertise in GB (base 10) while most software report size in GiB (base 2), but misleadingly label it as "GB".

It's like if storage companies measured in an improper unit like the quart while software measures using a proper unit like the liter but calls it a quart. Both sides are at fault. The storage companies (optical discs, hard disks, flash drives, and SSDs) insisting on using an improper base-10 unit because it makes their numbers look better. Software makers for mislabeling GiB, MiB, and KiB as GB, MB, and KB (the "i" makes it too confusing, they say... I say, humbug... the resulting unit confusion is much worse).

The 64GB M4 has 64,023,257,088 bytes. That's 64.02 GB. Or 59.63 GiB (or "GB", as Windows insists).
 
Don't ssd's also have extra swap space built in though? So you lose 7.3% + whatever swap space they have, right?

Just looked at my x25m 80 gb, it shows ad 75 gb in windows. That could be 5 gb reserved for swap space or it could be that 74.4 GB is the true size. Anybody know which one it is?
 
The 64 GB M4 drive has 64 GiB or binary Nand Flash even though it's advetised as GB the difference between the binary and base 10 64 GB figure is used as spare area.
 
Don't ssd's also have extra swap space built in though? So you lose 7.3% + whatever swap space they have, right?

Just looked at my x25m 80 gb, it shows ad 75 gb in windows. That could be 5 gb reserved for swap space or it could be that 74.4 GB is the true size. Anybody know which one it is?

The x25m 80 GB has 80 GiB of flash, and 80 GB of user accessible storage space. Windows registers it as 74.4 GiB of accessible space... which it displays incorrectly as 74.4 GB. The rest is reserved for whatever the SSD wants to use it for; bad blocks, swap, remapping, etc.

The 64 GB M4 drive has 64 GiB or binary Nand Flash even though it's advetised as GB the difference between the binary and base 10 64 GB figure is used as spare area.
This is correct. The confusion in units suck. I used to hate the binary GiB ("but gigabytes always meant 1024 megabytes!") but I've warmed up to its use since it's so easy to confuse them otherwise. Stupid Windows!

Does the M4 have exactly 64gb of usable space
Yes, if you accept that 1 GB = 1 000 000 000 bytes. But the key is that this is the user accessible ("usable") space.
 
GB was 2^24 before it was 10^9.

But SI defined "giga" to be 10^9 before programmers attached it to a prefix that was 2^24. 😛

Don't get me wrong; I hate the use of 10^9. But I also think that the prefix should disambiguate and be precise in its meaning.
 
Back
Top