Bug 429771 - After resizing the root partition the available space is not changed
Summary: After resizing the root partition the available space is not changed
Status: REPORTED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: Properties dialog (show other bugs)
Version: git master
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-28 18:08 UTC by Claudius Ellsel
Modified: 2020-12-01 17:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot showing the properties window of the drive (125.34 KB, image/png)
2020-11-28 18:13 UTC, Claudius Ellsel
Details
Result after updating the size information (60.43 KB, image/png)
2020-11-28 18:15 UTC, Claudius Ellsel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Claudius Ellsel 2020-11-28 18:08:05 UTC
SUMMARY
I changed the root partition on a virtualbox recently with the KDE partition manager. However the displayed available space for example in Dolphin did not change. Not sure what causes this, either the resize did not work properly or the way how the available space is calculated does not work in this circumstance.

It updates, but the values are updated in a way as if the disk size was still 8 GB, not 16 GB.
Comment 1 Claudius Ellsel 2020-11-28 18:13:20 UTC
Created attachment 133708 [details]
Screenshot showing the properties window of the drive

While the drive is displayed as 16 GB at other instances, the properties window still shows 8GB.
Comment 2 Claudius Ellsel 2020-11-28 18:15:53 UTC
Created attachment 133709 [details]
Result after updating the size information

After pressing the button to update the size information, it displays 128TiB there now, which is also wrong and probably related.
Comment 3 Claudius Ellsel 2020-11-28 19:58:24 UTC
After further expanding the disk space using gparted this time, everything seems to work as expected again. I still don't know what caused the problem here.
Comment 4 Claudius Ellsel 2020-11-28 20:05:46 UTC
Well, not everything. The 128 TiB problem is still there; created https://bugs.kde.org/show_bug.cgi?id=429781 for that now.