Hi Phillip,
With this problem recently cropping up, I do think that restoring the
code back to the way it was will fix this problem.
The reason is that the file system will be resized slightly smaller.
Then it will fit within the same partition size. In other words it is a
different way of tackling the problem. Instead of making the partition
bigger, we instead make the file system smaller.
There are some rounding operations in the code to ensure that ext2/3/4
resizing will match to an integer value of kiB. By removing the part
where 1 kiB is subtracted before the rounding operation, we have
inadvertently permitted the file system to be rounded up to 1 kiB more
than it would have been with the old code. We might have to think about
other sector sizes too now that 4k sector drives are becoming more
widely available.
At least those are my thoughts at the moment.
I would like to hear from Mike too because he was involved in this
recent change and might be able to shed more light on the subject.
Curtis
On 14-02-02 12:14 PM, Phillip Susi wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 02/02/2014 12:35 PM, Curtis Gedak wrote:
Hi Anomie and Phillip,
There was a recent change in GParted 0.16.2 that is directly
related to resizing ext2/3/4 file systems. Specifically the change
no longer subtracts 1 kiB from the file system size which would
have prevented this problem from occurring.
The relevant commit is:
Shrink file systems to exact size (#701075)
https://git.gnome.org/browse/gparted/commit/?id=3461413d283f1bac77e541b1054e775ec105212f
That's
resizing the filesystem. This case appears to be the partition
getting set to the wrong size.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
