I have increased the size of the partition of my Pop_OS installation (/nvme0n1p4) from 128 GB to 650 GB using Gparted (from the live USB stick). I have set it exactly to 650 GB.
But in Pop_OS I now have the problem that I am shown three different sizes:
- The command
fdisk -ltells me that the partition has a size of 634.8 GB. - The app “disks” tells me that the partition has a size of 682 GB.
- The app “Stacer” tells me the partition has a size of 624.2 GB.
I am now a bit confused and would like to ask you if anyone knows a solution or can at least tell me which indication is correct. I mean, if this indication is wrong, is the information at all correct, how much space of the SSD is already used? I also see different specifications there…
That’s really weird. But I can explain one value there:
You set it to 650 GB (1000 bytes), fdisk might show you GiB (1024 bytes) though. Which would be 634.8 GiB.
It’s the same as you buying a 1 TB disk and you only get a 977 GB partition out of it.
No clue about your other apps though, sorry.
thank you
Thanks for pointing me into this direction.
When I use an online calculator to convert Gibibytes to Gigabytes, I get this result: 634.8 GiB are 682 GB. So, exactly the size that the Gnome-Disk-Utility shows.
The App Stacer tells me 624.2 GiB. When I convert this into Gigabytes, I get 670.3 GB. This size is also shown in the Pop_OS file manager.
So, in conclusion:
- fdisk command and Gnome disk utility are showing 634.8 GiB / 682 GB.
- Stacer and file manager are showing 624.2 GiB / 670.3 GB.
One step closer… Now I just need to figure out why two apps are showing too less storage space compared to the other ones.
Could it be that Stacer and file manager are somehow reporting usable space instead of “absolute” space.
I recall from the early days that there was overhead in the process, so that useable space was always less than formatted space. Perhaps that is still the case.
