resize logic not 64-bit clean

[Stephen Gornick]

Binary package hint: ubiquity

When using the "Edit Partition" dialog box from Manual Partitioning, the range of values for setting the "New Partition Size in Megabytes" is 4700 to -2000 (from the spin value selectors). Any reason this couldn't be 4700 to 0 so that negative values cannot even mistakenly be selected?

Feisty Beta i386

[Colin Watson (cjwatson)]

That's pretty bizarre. I can certainly clamp the values, but I'd like to find out why this is happening in the first place. Could you please attach /var/log/syslog and /var/log/partman to this bug, following the directions in http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in advance.

[Stephen Gornick (sgornick)]

I ran
$ ubiquity --debug
and and selected Edit partition on the ext3 partition and tried to set the size to -1600. Note that this is on an extended (logical) partition.

[Colin Watson (cjwatson)]

Thanks!

partman-partitioning (47ubuntu5) feisty; urgency=low

  * Use expr in resize logic rather than assuming that shell arithmetic is
    64-bit clean, which it isn't in dash (LP: #95400).

 -- Colin Watson <email address hidden> Mon, 26 Mar 2007 13:58:59 +0100

[Andreas Schildbach (schildbach)]

I'm not really sure this is fixed. I upgraded to ubiquity 1.4.7, and now partition size indeed cannot be negative.

However, the smallest possible setting is 20% (~15 GB). Is this really intended? Ubuntu works in a partition as little as 3 GB!

[Tim Prosser (tim-prosser)]

Spotted the problem with the partition tool and logged it in #104311 before spotting it was a duplicate of this one.

Running apt-get install ubiquity before doing the install to get the latest version (installing from Beta DVD, 13th April) still doesn't lead to correct behaviour.

"Edit Partition" on an existing partition now selects 0 as the initial size, but when the mount point is changed, this is updated to the USED space on the partition, not the actual size. Odd!

See 104311 for more details.

Thanks.

[Roman Polach (rpolach)]

This problem is NOT fixed in Feisty Final!
1) When attempt to change mount-point, partition size is initialy set to "0",
2) then (after clicking into mount-point editbox) it has changed to "used size" value instead of "total size",
3) when attempt to manually fill correct value (25531), it changed it to 25500

This should be fixed by all of these steps:
a) allow to set correct (original) size and do not change it to some other value if it is valid!!
b) allow user change mount-point with different dialog than that with resize ability to not make user worry about destroying the partition only when he wants to assign mount-point!
c) predefine initial value shown to actual "total size"

I am very disappointed this critical bug is not fixed in final version..

[nitrogen (i-am-nitrogen)]

Marking this with an open state, as "Fix Released" doesn't quite describe the possibility of accidentally toasting a partition when one simply wants to set a mount point...

[Colin Watson (cjwatson)]

Guys, please file a NEW BUG against ubiquity about these problems rather than reopening this one. I don't want to attempt to diagnose them in this bug, since I did fix the problem described in the bug description.

Please remember to attach /var/log/syslog and /var/log/partman to your bug report, as described in http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs.

[Colin Watson (cjwatson)]

(I'm perfectly prepared to acknowledge that a problem still exists, but I'm also prepared to bet that it's not the same one and thus belongs in a different bug report.)

[Roman Polach (rpolach)]

Colin, this bug has 18 dupes. At least some of them describe
behavior, which is not fixed, so shouldn't they be un-duped?