GNOME Bugzilla – Bug 663980
Avoid redundant file system maximize actions on copy, move, and resize
Last modified: 2011-12-13 17:43:19 UTC
When GParted performs operations or combinations of operations, such as: a) copy to same or smaller size destination partition b) move to same or smaller size due to alignment change c) resize to smaller size a redundant maximize file system operation occurs. Normally these redundant maximize operations to grow the file system to take up all the space in the partition are not harmful. However in situations where libparted fails to inform the kernel of partition changes, then the extra maximize operation can grow the file system to be the original partition size. In cases where the original partition was larger than the new partition size, this causes problems because the file system will be larger than the partition on reboot. If these redundant maximize file system operations are removed, then this would reduce problems described in the following links: WARNING! Problem Resizing File Systems with GParted http://gparted-forum.surf4.info/viewtopic.php?id=13777 Bug #601574 - ERROR: Current NTFS volume size is bigger than the device size! Bug #604298 - Problems resizing file systems with gparted-live-0.5.0-3
An enhancement to avoid redundant file system maximize actions on copy, move, and resize has been committed to the gnome git repository for inclusion in the next release of GParted. The relevant git commit can be viewed at the following link: http://git.gnome.org/browse/gparted/commit/?id=e8bdb5d7045f71fc19ba8e4651906cdd47ac6774
The enhancement to address this bug report has been included in GParted 0.11.0 released on Dec. 13, 2011.