https://bugs.kde.org/show_bug.cgi?id=396705
--- Comment #2 from Martin Anantharaman <martin.ananthara...@web.de> --- Sorry for being cryptic, so this time I try to give you the whole picture: - Disk has 931,5GB of which 603GB was used in one EXT4 partition, but I needed to create a new partition, so I wanted to shrink the existing partition as much as possible and shift it to the end. - So, existing Filesystem was used to about 603 GB - which is the "minimum size" partitionmanager (and GParted) allowed for the resize. - I chose 605GB (to have a bit of space to create listings and such till I was completely done) but the resize2fs task failed because resize2fs only permitted resizing to about 655GB. I determined this by running resize2fs -M - and in later operations first ran resize2fs -P and used that estimate as input to partitionmanager. As I said, resize2fs seems to estimate substantial filesystem-overhead (see 655GB vs. 603GB). I did not take the time to check code but it would seem that partitionsmanager (and GParted) should ask resize2fs what it is willing to do as the new size must take into account not only data but also filesystem data-structures whose size is not obvious. Regards, Martin -- You are receiving this mail because: You are watching all bug changes.
