After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 463684 - Can't grow partition size larger than 1 TB.
Can't grow partition size larger than 1 TB.
Status: RESOLVED DUPLICATE of bug 524948
Product: gparted
Classification: Other
Component: application
Other All
: Normal normal
: ---
Assigned To: gparted maintainers alias
gparted maintainers alias
Depends on:
Reported: 2007-08-05 16:11 UTC by gparted.8.sc00p
Modified: 2008-04-25 14:24 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description gparted.8.sc00p 2007-08-05 16:11:49 UTC
Please describe the problem:
When trying to grow a partition approximately 900 GB in size to approximately 1.2 TB, I receive the following error message:

"Could not add this operation to the list. A partition cannot have a length of -1 sectors."

If I attempt to resize it to any value under 1 TB, it will not give the error message.

The filesystem on that partition is a JFS filesystem.

Steps to reproduce:
1. Select the disk.
2. Select Partition->Resize/Move
3. Increase the new size to 1048576 or more.

Actual results:
I receive the following error message:

"Could not add this operation to the list. A partition cannot have a length of -1 sectors."

Expected results:
It should add a pending operation to the list.

Does this happen every time?

Other information:
Comment 1 Armand MacMurray 2007-09-13 18:02:33 UTC
This bug also happens when trying to create a new partition larger than 1TB (at least for ext2, ext3, xfs filesystems).
Comment 2 cs 2008-01-23 18:27:39 UTC
I have seen something similar (using LiveCD of GParted 0.3.3) -- I wished to resize an ext2 partition on my 2TB ext LaCie drive [NB#1] and when I view it in GParted it thinks it has -198618708992B (ie a negative number) according to top right (drop down list of devices), although the display has 1.82TiB and then the info for the (only) partition [size 1.82TiB with used=1,55TiB & unused= 272.77GiB] all of which sound about right.

I tried to resize (to smaller so could add another partition) but it failed :(

More info: if I open up the terminal (from the GParted LiveCD) and run fdisk it gives 2000.4GB for the disk with start=1 end=243202 and blocks=1953520064+ (not sure what the plus signifies)

I did try other commands to resize (fdisk or sdisk but it was complaining about unsupported)

This is on my AMD64 box with the drive connected with Firewire 400.

[NB#1] how did I originally partition to all of the disk to ext2? I wish I could remember but it may have been sdisk/fdisk/parted or another Linux tool (and it would have been using USB connector and a Intel Core2 Duo box)
Comment 3 Curtis Gedak 2008-04-21 17:16:18 UTC
Thank you all for the details on this bug report.

Work on this bug has been progressing under bug #524948.  My preference is to use the first report of the bug as the base, and then mark any new reports as duplicates.  Unfortunately I overlooked this one (there were more than 100 GParted bugs when I started :-).  Hence I am marking this bug as the duplicate.

The good news is that the problem has been identified and a fix created :D

Curtis Gedak (new C++ Developer for GParted)

*** This bug has been marked as a duplicate of 524948 ***
Comment 4 gparted.8.sc00p 2008-04-22 00:01:59 UTC
Curtis, thanks for working on this.  I have downloaded the svn and am testing it out.  It looks like it is going to work this time; at least, I didn't think it let me get this far before.

Comment 5 gparted.8.sc00p 2008-04-24 21:53:35 UTC
I can confirm that svn resolved my issue.
Comment 6 Curtis Gedak 2008-04-25 14:24:43 UTC
Thank you Greg for testing the SVN version and confirming that the bug is fixed.  :-)