On 14-02-05 11:14 AM, Phillip Susi wrote:
I believe that -1 was masking the real error, which is in the
partition resize code, since the new size of the partition is not an
even multiple of 4k. The end sector also is not aligned to a 1 MiB
boundary.
Good catch Phillip.
This operation is a shrink and move, and the temporary location of the
shrunken file system is not the final destination. Having said that I
think there might be a problem with the final location not being MiB
aligned.
With the commit reverted, the next step in the gparted_details.htm log
file is to grow the partition to an all-encompassing partition and this
end sector value is _not_ MiB aligned.
Log file snippet follows.:
grow partition from 342.80 GiB to 1.82 TiB 00:00:01 ( SUCCESS )
old start: 2048
old end:
old size: 718893231 (342.80 GiB)
new start: 2048
new end: 3907029166
new size 3907027119 (1.82 TiB)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
