66 comments

log in to comment.

  • @bacon_pdp@lemmy.world · 5 Nov 2026

    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.

    • @kkj@lemmy.dbzer0.com · 5 Nov 2026

      The problem arises when the OS uses GiB but labels them GB, like Windows does.

      • @sik0fewl@piefed.ca · 6 Nov 2026

        No, the problem is making up a new word (gibibyte) and expecting people to use it when there’s already a word for that (gigabyte).

        It’s the hard drive manufacturers that should change.

        • @BitUnWise@programming.dev · 6 Nov 2026

          I want to agree with you, but the war is lost. Giga is billion and Gibi is 2^30

          • @Olmai@lemmy.world · 7 Nov 2026 · edited

            I want to agree with you two, because I hate competing standards, but you gotta admit gigabyte was a poor choice from the start because it took the SI prefix and made it mean something else. Creating Gibi is just correcting that mistake

            • @SpaghettiMaster@feddit.uk · 7 Nov 2026

              Agreed, metric prefixes should always remain consistent. Computers can read both though, so why doesn’t windows?

        • @ulterno@programming.dev · 8 Nov 2026

          Let’s see someone willing to give you 1024g of gold for the price of 1Kg gold.

    • @cenzorrll@piefed.ca · 5 Nov 2026

      Look at Mr. “100 IQ” over here

    • @Ephera@lemmy.ml · 5 Nov 2026

      Yeah:

      1000 GB × 1000 × 1000 × 1000 / 1024 / 1024 / 1024 = 931.32 GiB

      It’s a sufficient explanation. I don’t know why the meme has the highest IQ person say “I don’t know”, unless the joke is that it’s easier than explaining…

      • @skisnow@lemmy.ca · 7 Nov 2026

        I don’t know why the meme has the highest IQ person say

        Every time I see the midwit meme format, it reads like OP imagines that they’re the 145 IQ guy who is above it all, when all other evidence suggests that they’re closer to the 55 IQ guy.

      • @bearoftheisle@europe.pub · 6 Nov 2026

        I’m guessing that IDK is for why they write it as GB and not GiB

      • @Tlaloc_Temporal@lemmy.ca · 6 Nov 2026

        Because there are other things that change usable space, like file tables, OS stuff, and bad sectors. The unit conversion is the biggest one, but not the only one.

    • @Redjard@reddthat.com · 6 Nov 2026

      Which itself is for marketing reasons, a manufacturer would find it difficult to compete with others using units that make their drives look larger or cheaper at “same capacity”.

      There is also the smaller amount w!ndows will secretly waste for its own pleasure (few GiB iirc). And an even smaller amount that gets wasted in partitioning. Usually around 5MiB, you can reduce it to 16kiB with some manual configuration in gdisk, or you can skip partition tables entirely for some end-game cursedness. And then the filesystem will take some. ext4 takes based on the number of inodes, for large drives that can be tens of GiB. Btrfs takes almost nothing (though in the background allocates in steps of 1GiB, so some tools might show 2GiB used as soon as data is written). Then if you try to sum all files on disk, that will land even lower for many more reasons.

    • @heartSagan5@lemmy.zip · 5 Nov 2026

      And it gets more complicated when we get to the metadata and filesystem structure. So, you technically never get to store 931GB, I wonder what the (average) ratio of metadata to data is? 3:1?

      • @bacon_pdp@lemmy.world · 5 Nov 2026

        Depends on the file system. If you are using FAT-8; it is 256:1 if you are on ZFS it is as low as 1:4.

        It also depends on composition of the data stored. If it is Linux ISOs; it is 4GB:64KB. If it is old C source code; it is 512B:4KB on ext4

    • @Valmond@lemmy.dbzer0.com · 5 Nov 2026

      At the beginning of time, K/M/G etc was based on 1024. This was considered a bad move by some people.

      What I don’t get is memory packages don’t come in thousands, but in volumes dividable by 1024, so why the 1TB=1000 somethings…

      • @bacon_pdp@lemmy.world · 5 Nov 2026

        Because back in the 1980s RAM chips were individually sold and the number of address pins exactly matched the 2^(# of pins) amount of memory addresses contained in the chip (for cost savings purposes) and only with the later column strobe addressing DRAM did that change but at that point they couldn’t deviate from the 1024 standard without getting sued (a couple did and went out of business).

        And since the RAM chips themselves are stuck using 1024 and the RAM sticks are made of matching RAM chips (for cost and performance reasons); it will remain that way until people start buying systems on a chip with embedded RAM.

    • @Agent641@lemmy.worldOP · 6 Nov 2026

      I’d just like to point out that while I understand the reason, I’m just not willing to explain that to people anymore in all them words so now I just say IDK

  • @Skullgrid@lemmy.world · 5 Nov 2026

    Bootlickers will then argue it’s cool that the manufacturer screws you out of almost a hundred gigs.

    • @kkj@lemmy.dbzer0.com · 5 Nov 2026

      The manufacturer is labeling the drive correctly as 1TB (1000GB, 10^(12)B). It’s Microsoft that incorrectly labels it as 931GB; it’s actually 931GiB (931 * 2^(30)B). A Mac will correctly show 1000GB and a Linux machine will correctly show 931GiB.

      • @protogen420@lemmy.blahaj.zone · 5 Nov 2026

        Linux uses the unit defined by your locale, it may vary

        • @kkj@lemmy.dbzer0.com · 5 Nov 2026

          I’ve seen GB sometimes on Linux, but they’re actual GB, not mislabeled GiB, so I don’t have a problem with it.

      • @Skullgrid@lemmy.world · 5 Nov 2026

        Told you guys.

        • @kkj@lemmy.dbzer0.com · 5 Nov 2026

          “Bootlickers will blame a multi-trillion-dollar company”

          Do you know what that word means?

          • @Skullgrid@lemmy.world · 5 Nov 2026

            If any company could get away with labelling their product to have 1/10th less and get away with it, they would. Usually consumer rights organisations fight to make it so that you get what is advertised.

            The producers are using semantics to give less. I, as a customer want what I have been promised by the label.

            If you’re interested in arguing the opposite, you’re anti-customer, and pro-ripoff.

            • @TheNamlessGuy@lemmy.world · 6 Nov 2026

              [deleted]

              • @Skullgrid@lemmy.world · 6 Nov 2026 · edited

                fastfetch output :

                Disk (/): 203.45 GiB / 224.94 GiB (90%) - ext4
                Disk (/media/skullgrid/Data): 684.44 GiB / 913.43 GiB (75%) - fuseblk
                

                I didn’t realise that Linus Torvalds changed his name…

                … unless you think I specifically went out and bought a laptop that advertised a 913.43 GiB secondary drive?

                • @ulterno@programming.dev · 8 Nov 2026

                  Now I understand why the 100 IQ guy up there is crying.
                  Because even after you see the literal ‘i’ in between, you will still call them the same.

                  It’s as if you bought a metric ton of grain just to then complain that is doesn’t match an imperial tonne.

                • @TheNamlessGuy@lemmy.world · 8 Nov 2026

                  [deleted]

    • @eager_eagle@lemmy.world · 5 Nov 2026

      since it’s 69GB it’s not cool, it’s nice

    • @jacksilver@lemmy.world · 5 Nov 2026

      They should just be requires to use consistent units of measurement.

  • @eah@programming.dev · 5 Nov 2026

    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.

    superuser.com/…/why-does-my-500gb-hard-drive-have…

  • @noobface@lemmy.world · 5 Nov 2026

    You will never hear me say gibibytes in public though. Telling on my nerdy ass self is for private conversations.

  • @Hamknight@lemmy.world · 5 Nov 2026

    The old GiB vs GB

    • @Ooops@feddit.org · 5 Nov 2026

      Plus some programs showing space actually usable for your data (not unreasonable from user perspective), which means another chunk is gone as overhead from the file system.

  • @Infernal_pizza@lemmy.dbzer0.com · 5 Nov 2026

    Its great when you buy larger capacity drives and start to lose entire terabytes

    • @nuko147@lemmy.world · 5 Nov 2026

      Technically you dont lose anything. Its like you buy a car with top speed in Kmh, but you see Mph when you drive.

      • @Infernal_pizza@lemmy.dbzer0.com · 5 Nov 2026

        Yeah I know it’s technically the correct use of terabyte vs tebibyte but it still feels bad when your 12TB drive is only 10.9TiB

        • @nuko147@lemmy.world · 5 Nov 2026 · edited

          Well it is too bad the Windows sucks. If only they had the money to make a proper OS that gives you the option to switch from binary to decimal like in Linux.

      • @lord_ryvan@ttrpg.network · 9 Nov 2026

        If a car was marketed “150 Mph” and it’s actual 150 Kph I’d feel pretty stolen from

  • @Shartyfartblast@piefed.zip · 5 Nov 2026

    SSDs also have over-provisioning (which is not a bad thing imo)

  • @eager_eagle@lemmy.world · 5 Nov 2026

    That’s your OS using base 2 units and calling it TB. The drive ships with 1TB.

  • @bstix@feddit.dk · 5 Nov 2026

    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?

    • @solarspark@lemmy.ml · 5 Nov 2026

      Be the change you want to see, and report back 😅

      • @bstix@feddit.dk · 5 Nov 2026 · edited

        I already did it on floppies.

        I also attempted to program the entire AD&D rules as an Amiga Basic program. It ran well for a start, but then I noticed that the random generator always returned the same dice rolls. Turned out that the RAM was used up, so it couldn’t store the random value anywhere. The program was fine otherwise. Just out of ram.

        Anyway, I miss the ingenuity of having too little space, more than I am impressed with the possibilities of having too much.

        People simply did more with less. I want that to return. The bloat is obscene, and hopefully AI is going to break the balloon of it. Nobody really needs several gigabytes of code to run a 2 line program.

    • @MonkderVierte@lemmy.zip · 7 Nov 2026

      I mean, it doesn’t? The last few GB get slow.

  • @Hupf@feddit.org · 7 Nov 2026
    • @ulterno@programming.dev · 8 Nov 2026 · edited

      Guess I’ll make sure to buy my HDDs packaged during non-leap years.
      Oh…SH…Wt… I should have bought them all out over 100 years ago!

  • @liinux@pawb.social · 5 Nov 2026

    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!

    • @driftwood@lemmy.zip · 5 Nov 2026

      FML you’re telling me I need Random Access Memory Memory now? 😩 Never getting a new pc.

    • @milbyte11@lemmy.ml · 5 Nov 2026

      is there something wrong with RAM on windows? iirc this was one of the things that worked normally for me.

  • @MonkderVierte@lemmy.zip · 7 Nov 2026 · edited

    Bits sold as bytes.

  • @ulterno@programming.dev · 8 Nov 2026 · edited
    > 1TB to TiB
    
      1 terabyte ≈ 0.9094947018 TiB
    
    

    Brought to you by libqualculate.

    Guess the middle guy is crying because he is wrong.


    Had some fun:

    > 1TiB to B to bin
    
      1 tebibyte = 0000 0000 0000 0000 0000 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 B
    
    > 1TB to B to bin
    
      1 terabyte = 0000 0000 0000 0000 0000 0000 1110 1000 1101 0100 1010 0101 0001 0000 0000 0000 B
    

    Ok just realised it was GiB and not TiB, so the guy on the top was right.

  • @purplemonkeymad@programming.dev · 6 Nov 2026

    This is why the first large drive I bought was actually 1.5, so that I got to see that sweet T.

    • @ulterno@programming.dev · 8 Nov 2026
      I bought a 2.

      Because reviews said that that model was more reliable.

      • @purplemonkeymad@programming.dev · 9 Nov 2026

        They were right. It was also one of the first drives to fail on me.

        • @ulterno@programming.dev · 9 Nov 2026

          Yeah, at the time, Seagate Expansion 1.5 TB and 4 TB drives were going bad quite a bit and WD was shipping drives with the USB-SATA non-removable, which meant that damage to the adapter would make the data unrecoverable.
          The 2 TB one survived quite a bit and even when I used a bad USB C to USB A adapter and damaged the USB-SATA adapter, I could still recover data and use the drive for a few more years.

  • @lord_ryvan@ttrpg.network · 9 Nov 2026

    Now, why does my drive have 928GiB instead of 1TB or 1TiB? That I don’t know

  • @Kolanaki@pawb.social · 9 Nov 2026

    There’s always gonna be a small little file on the drive telling the system how to use the drive or whatever. They should account for this, and make drives just that bit larger so you get the exact advertised capacity after that file is created.

  • @Blibittyblah@futurology.today · 5 Nov 2026

    Mother decides she’s so tired of educating her responsibility that she stops educating them altogether and finds they are ultimately more controllable when they stop having knowledge. 🇺🇸🇷🇺🇨🇳