>buy hard drive that is advertised as 4TB
>it actually only has 3.5TB space
why the fuck is this allowed?
>>51856064
joos.
>>51856064
if the drive requires some shit on it to work, then it should be subtracted from the stated amount
the fcc or some shit should do something
>>51856064
are you using windows? microsoft counts KB/MB/GB/TB the wrong way.
by definition, those are SI-prefixes. kilo for 1000, mega for 1000000 etc.
microsoft uses 1024 (2^10) as a base instead, which is simply wrong. these units exist too, but they're called KiB, MiB, GiB, TiB etc. those are binary prefixes.
>>51856064
It's Microsoft lying about the disk space to make you buy bigger hard disks. Fuck those jews.
Ask Nvidia :^)
>>51856082
>microsoft counts KB/MB/GB/TB the wrong way.
No it doesn't.
>>51856064
GB != GiB
What are you? Stupid?
>>51856082
GNU+Retard detected.
>>51856098
yes they fucking do.
a terabyte is supposed to be 1000 * 1000 * 1000 * 1000 = 10^12 = 1000 000 000 000 = 1 trillion bytes
for M$, a terabyte is 1024 * 1024 * 1024 * 1024 = 2^40 = 1099 511 627 776 = more than a trillion bytes
it's wrong. that should be called a tebibyte (TiB).
https://en.wikipedia.org/wiki/Metric_prefix#List_of_SI_prefixes
>>51856082
This.
>>51856131
Is that it? Are Wintards the Americans of the software world?
>buy GPU that is advertised as 4GB
>it actually only has 3.5GB ram
>>51856120
This.
SI vs base 2 units.
>>51856098
Well, it's not that it counts wrong but rather, they display it wrong.
>>51856082
>>51856120
This argument never gets old...oh wait it isn't
Writing KB as KiB was a retarded idea from about 10 years ago, before that KB was always defined as 1024 bytes
>inb4 hard drive shills will defend this
>>51856179
Damn son, it's displaying right. Computers use base 2 prefix. Blame the hdd manufacturers.
>>51856181
SI-prefixes were defined long before all of this. using existing prefixes but changing their meaning is retarded.
>>51856186
>Computers use base 2 prefix
I know that. But displaying 500GB as 465GB, even though it's GiB, IS an erroneous display. I've seen this only on Windows as GNU/Linux doesn't have this problem (at least not on the file managers I have used).
Why would anyone blame the manufacturer if they do it correctly? 4TB = 4 * 2^40 Bytes which is what they promised to deliver.
>>51856144
Why is it 3,000,573,620,224 and not an even 3,000,000,000,000?
>inb4 OCD fag detected
>>51856228
Yeah, bytes should never have been treated as fucking SI units. They can't be negative and can only be whole numbers, and are describing base 2.
I'm guessing they used SI prefix because kilo/mega/etc. is familiar, and they didn't want to invent new prefixes purely for use with bytes, but it pretty much backfired somewhat. I still blame HDD manufacturers though, as they're the only people pushing for this; this problem doesn't exist with RAM.
Also OP is a retard because it clearly said on the packaging that 4TB = 4,000,000,000,000 bytes.
>>51856082
>uses 1024 (2^10) as a base instead, which is simply wrong
Found the child and/or marketing drone
>>51857256
using 1024 and calling it kilo is wrong. kilo is defined as 1000. deal with it.
>>51856064
That's what you get for buying nvidia :^)
Even with the TB vs TiB reasoning.
You can't expect to utilise the full 2TB, since probably some bytes will be damaged by transport, filesystem,... .
>>51857285
"mega" doesn't equal a million in the English language in any other context, so using it to mean a million of something in computer tech doesn't make sense either. Deal with it.
>>51856154
Underrated.
>>51857754
>what are megapixels
>what are megajoules
>what are megahertz
>what are megatons
>>51856181
>before that KB was always defined as 1024 bytes
Which is undeniably wrong.
>>51857754
retard
>>51857795
Where do I upvote?
>>51857809
When the entire foundation of the operation of the machine is based on baes 2 numeration it is undeniably [spoiler]right[/spoiler]
>>51857916
using base 2 isn't wrong. calling it kilo when it isn't kilo (1000) IS wrong.
>Buy 2TB
>Get 2TB
It just werks
>>51856313
what are you saying, on linux it sayd 465gib
or does it display 500gb ?
>>51856445
>bytes should never have been treated as fucking SI units
what?
its a quantitative prefix, the thing you're measuring doesnt have to fit any description
>>51857795
megapixels and megatons arent units though
using it in a phrase "Nixon sent a 250 teragrams H-bomb to give children cancer"
>>51857656
yeah, and who needs more than 640kilogram of dram
>buy a 1tb seagate "portable drive"
>put my animus and tv shows on there
>mom asks for it so that she can put her pictures on there
>ok
>a while later try to put something on there
>says I don't have the permission to that
>works only on windows now
>>51856120
GB = 1024 MB
GiB = bulshit meme that only appeared a few years back
>>51856134
It's called a tebibyte you inbred
>>51858349
Lrn2man
chmod
chown
>>51858363
you don't get to redefine international standards that have existed since the 18th/19th century.
giga == million
>>51858383
isn't that exactly what the post said?
>>51858363
Giga-X = 1 billion X
It's a standard.
>>51858404
Mega==million actually
>>51858389
I'm not a retard, I tried that.
>>51858363
What...are you fucking retarded? They created that Gibi shit just for this very purpose, to prevent confusion. That is not a fucking meme that magically appeared a few years back. Control your ignorance.
>>51858418
yeah, was supposed to be billion instead of million
>>51856064
The use of gigabyte is thus ambiguous. For semiconductor RAM, the gigabyte denotes 1073741824bytes. For hard drive capacities as described and marketed by the drive manufacturers, the gigabyte denotes 1000000000bytes, but when a 500-GB drive's capacity is displayed by, for example, Microsoft Windows, it is reported as 465 GB, where GB then means 1073741824bytes.
>>51858232
Linux file managers will show it as 500 GB volume normally
>>51856064
>buy hard drive that is advertised as 4TB
>it actually has 3.638 TiB
Works as advertised.
>>51858363
I bet you think there are 1024 meters in a kilometer.
Protip: you can't redefine technical terms just because you're retarded, that's how you end up losing a $125 million dollar spacecraft.
>>51858424
It pretty much just added confusion. Everybody knew that kilo/mega/giga in computer terminology stands for 1024. Now when somebody says megabyte, it raises the question if he meant mega as in 1000KB or mega as in 1024KB.
Filesystem and os.
>>51858926
either he meant 1000 or he's a retard and it doesn't matter what he said anyways.
>>51858971
You mean mebi right?
>>51858926
When someone says 1 megabyte you should assume it as 1000KB. When someone says 1 mebibyte youre sure its 1024 KiB.
There's no confusion, only if you're making it confusing. Every harddrive is measured in the SI method, only Windows displays it wrongly.
>>51858349
>HUR DUR I CAN'T CHANGE FILE PERMISSIONS.
Macfag spotted.
>>51858420
No you didn't, otherwise you wouldn't have made that post.
Sorry m8 but an OS can't "lock" a drive, it just doesn't happen.
I use all 3 operating systems and I've never had this problem, you fucked up somewhere.
>>51859092
>only Windows displays it wrongly
Yes, that's why RAM sticks are marketed as having 4GiB... Oh wait, they aren't. They are marketed as 4GB despite having 4096MiB.
>3.5TB
>>51856064
because you use a kek operating system
>>51859165
Memory and storage aren't the same. Can't compare pounds (weight) and pounds (british currency) either.
>>51856154
>microsoft doesn't follow hard drive shills and change the definition of GB
>microsoft is the wrong one
Okay, /g/
>>51859643
What about Toshiba?
>want to buy 50 liters of gas
>get 13.21 US gallons
why the fuck is this allowed?
>>51859643
Ah shit I just told my mommy "buy me a hard drive" without any details. How fucked am I?
>>51857959
Sorry mate but hard drive must have reserved sectors and space for function and fail over. You have edited that picture...
>>51859643
http://www.tweaktown.com/articles/6028/dispelling-backblaze-s-hdd-reliability-myth-the-real-story-covered/index.html
>>51857754
