GNU bug report logs -
#33634
Strange behavior from gparted
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 33634 in the body.
You can then email your comments to 33634 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-parted <at> gnu.org
:
bug#33634
; Package
parted
.
(Wed, 05 Dec 2018 20:07:05 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
"Brent W. Baccala" <cosine <at> freesoft.org>
:
New bug report received and forwarded. Copy sent to
bug-parted <at> gnu.org
.
(Wed, 05 Dec 2018 20:07:06 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi -
I just using gparted 0.32.0 on Ubuntu Bionic 18.04 to move and resize a
partition.
Initially, there was a 25 GB partition and a 100 GB partition followed by a
574 GB partition. The operation was to remove the 25 GB and 100 GB
partitions, move the 574 GB partition backwards to align with the old
partition's start, and resize the new partition to approx 698 GB.
Take a look at the attached gparted_details.htm. It looks like after the
old partitions were deleted, the 574 GB partition was moved and resized to
698 GB in one step, then resized back to 574 GB, then resized again to 698
GB.
Everything worked out fine, but this looked to me like some kind of bug, so
I thought it was best to report it.
agape
brent
[Message part 2 (text/html, inline)]
[gparted_details.htm (text/html, attachment)]
Information forwarded
to
bug-parted <at> gnu.org
:
bug#33634
; Package
parted
.
(Wed, 05 Dec 2018 21:32:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 33634 <at> debbugs.gnu.org (full text, mbox):
The details posted are as expected. This behaviour is not a bug.
GParted performs the "move/resize" action internally as two separate
steps: a move operation, and a grow operation.
For the move: GParted resizes the partition to be an all-encompassing
partition, moves the file system within the partition, and then shrinks
the partition to fit the file system.
For the grow: GParted resizes the partition to be an all-encompassing
partition, then grows the file system to fill the partition.
These two separate steps are common to all file systems actions and are
kept separate for simplicity and consistency in the code. The reason
being that while some file systems like ext2/3/4 have file system
specific commands for moving, such as e2image, others must rely on
GParted to perform it's own internal move operation.
'Hope that helps explain what occurred and why.
Regards,
Curtis Gedak
On 2018-12-05 12:52 p.m., Brent W. Baccala wrote:
> Hi -
>
> I just using gparted 0.32.0 on Ubuntu Bionic 18.04 to move and resize a
> partition.
>
> Initially, there was a 25 GB partition and a 100 GB partition followed by a
> 574 GB partition. The operation was to remove the 25 GB and 100 GB
> partitions, move the 574 GB partition backwards to align with the old
> partition's start, and resize the new partition to approx 698 GB.
>
> Take a look at the attached gparted_details.htm. It looks like after the
> old partitions were deleted, the 574 GB partition was moved and resized to
> 698 GB in one step, then resized back to 574 GB, then resized again to 698
> GB.
>
> Everything worked out fine, but this looked to me like some kind of bug, so
> I thought it was best to report it.
>
> agape
> brent
>
Reply sent
to
Phillip Susi <phill <at> thesusis.net>
:
You have taken responsibility.
(Tue, 23 Apr 2019 15:21:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
"Brent W. Baccala" <cosine <at> freesoft.org>
:
bug acknowledged by developer.
(Tue, 23 Apr 2019 15:21:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 33634-done <at> debbugs.gnu.org (full text, mbox):
Closing bug since it is unrelated to parted, and not a bug.
Brent W. Baccala writes:
> Hi -
>
> I just using gparted 0.32.0 on Ubuntu Bionic 18.04 to move and resize a
> partition.
>
> Initially, there was a 25 GB partition and a 100 GB partition followed by a
> 574 GB partition. The operation was to remove the 25 GB and 100 GB
> partitions, move the 574 GB partition backwards to align with the old
> partition's start, and resize the new partition to approx 698 GB.
>
> Take a look at the attached gparted_details.htm. It looks like after the
> old partitions were deleted, the 574 GB partition was moved and resized to
> 698 GB in one step, then resized back to 574 GB, then resized again to 698
> GB.
>
> Everything worked out fine, but this looked to me like some kind of bug, so
> I thought it was best to report it.
>
> agape
> brent
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 22 May 2019 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 312 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.