[debbugs-tracker] bug#33634: closed (Strange behavior from gparted)

From:

GNU bug Tracking System

Subject:

Date:

Tue, 23 Apr 2019 15:21:02 +0000

Your message dated Tue, 23 Apr 2019 11:20:43 -0400 with message-id <address@hidden> and subject line Re: bug#33634: Strange behavior from gparted has caused the debbugs.gnu.org bug report #33634, regarding Strange behavior from gparted to be marked as done. (If you believe you have received this mail in error, please contact address@hidden) -- 33634: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=33634 GNU Bug Tracking System Contact address@hidden with problems

--- Begin Message --- Subject: Strange behavior from gparted Date: Wed, 5 Dec 2018 14:52:52 -0500

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

GParted 0.32.0 --enable-libparted-dmraid --enable-online-resize

Libparted 3.2

Delete /dev/sda1 (fat32, 25.00 GiB) from /dev/sda 00:00:02 ( SUCCESS )

calibrate /dev/sda1 00:00:01 ( SUCCESS )

path: /dev/sda1 (partition)
start: 2048
end: 52430847
size: 52428800 (25.00 GiB)

delete partition 00:00:01 ( SUCCESS )

========================================

Delete /dev/sda2 (ntfs, 100.00 GiB) from /dev/sda 00:00:01 ( SUCCESS )

calibrate /dev/sda2 00:00:00 ( SUCCESS )

path: /dev/sda2 (partition)
start: 52430848
end: 262146047
size: 209715200 (100.00 GiB)

delete partition 00:00:01 ( SUCCESS )

========================================

Move /dev/sda3 to the left and grow it from 573.64 GiB to 698.63 GiB 06:03:06 ( SUCCESS )

calibrate /dev/sda3 00:00:00 ( SUCCESS )

path: /dev/sda3 (partition)
start: 262146048
end: 1465149167
size: 1203003120 (573.64 GiB)

check file system on /dev/sda3 for errors and (if possible) fix them 00:03:54 ( SUCCESS )

e2fsck -f -y -v -C 0 '/dev/sda3' 00:03:54 ( SUCCESS )

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

3085849 inodes used (8.21%, out of 37601280)
8567 non-contiguous files (0.3%)
2716 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 3025852/1797/21
150258992 blocks used (99.92%, out of 150375390)
0 bad blocks
42 large files

2709390 regular files
306947 directories
119 character device files
50 block device files
17 fifos
3223 links
69182 symbolic links (57850 fast symbolic links)
135 sockets
------------
3089063 files

e2fsck 1.44.4 (18-Aug-2018)

grow partition from 573.64 GiB to 698.64 GiB 00:00:01 ( SUCCESS )

old start: 262146048
old end: 1465149167
old size: 1203003120 (573.64 GiB)

new start: 2048
new end: 1465149167
new size: 1465147120 (698.64 GiB)

move file system to the left 05:55:08 ( SUCCESS )

e2image -ra -p -o 134217728000 '/dev/sda3' 05:55:08 ( SUCCESS )

e2image 1.44.4 (18-Aug-2018)
Scanning inodes...
Copied 150254570 / 150254584 blocks (100%) in 05:53:48 at 27.65 MB/s s

shrink partition from 698.64 GiB to 573.64 GiB 00:00:01 ( SUCCESS )

old start: 2048
old end: 1465149167
old size: 1465147120 (698.64 GiB)

new start: 2048
new end: 1203005167
new size: 1203003120 (573.64 GiB)

check file system on /dev/sda3 for errors and (if possible) fix them 00:03:46 ( SUCCESS )

e2fsck -f -y -v -C 0 '/dev/sda3' 00:03:46 ( SUCCESS )

e2fsck 1.44.4 (18-Aug-2018)

grow partition from 573.64 GiB to 698.63 GiB 00:00:01 ( SUCCESS )

old start: 2048
old end: 1203005167
old size: 1203003120 (573.64 GiB)

new start: 2048
new end: 1465145343
new size: 1465143296 (698.63 GiB)

grow file system to fill the partition 00:00:15 ( SUCCESS )

resize2fs -p '/dev/sda3' 00:00:15 ( SUCCESS )

Resizing the filesystem on /dev/sda3 to 183142912 (4k) blocks.
The filesystem on /dev/sda3 is now 183142912 (4k) blocks long.

resize2fs 1.44.4 (18-Aug-2018)

========================================

--- End Message ---

--- Begin Message --- Subject: Re: bug#33634: Strange behavior from gparted Date: Tue, 23 Apr 2019 11:20:43 -0400 User-agent: mu4e 0.9.18; emacs 25.2.2

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

--- End Message ---

[Prev in Thread]

Current Thread

[Next in Thread]

[debbugs-tracker] bug#33634: closed (Strange behavior from gparted), GNU bug Tracking System <=