[Bug 1067841] Re: funky resizing on lubuntu ppc alternate quantal 20121017

Simon Quigley tsimonq2 at ubuntu.com
Thu Apr 5 03:14:21 UTC 2018


Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1067841

and any other logs that are relevant for this particular issue.

** Changed in: partman-auto (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to partman-auto in Ubuntu.
https://bugs.launchpad.net/bugs/1067841

Title:
  funky resizing on lubuntu ppc alternate quantal 20121017

Status in partman-auto package in Ubuntu:
  Incomplete

Bug description:
  trying to do the guided resize testcase, the first thing to check is
  that the initial value given is 50%. so when i start out i read
  minimum is 1.9 GB (1%) and max is 157.6 GB with the initial value
  being 79.8 GB whereas 50% of 157.6 GB is 78.8 GB. after resizing, the
  partition table reported the 79.8 GB value.

  next thing to do is to check the minimum size. so i try 1% and i get
  an error that it's smaller than minimum. i try typing just 1.9 and,
  again, too small (does it assume KB?). then i try 1.9 GB and it works
  fine. after resize, the partition table reported 1.9 GB.

  so now i'm tasked to do a resize to the maximum and i can't. my only
  option is to reuse the 1.9 GB partition. so i made a new partition out
  of the free space and i was given min 512 MB (0%), max 157.1 GB and
  again i get an initial value of 78.6 GB whereas 50% is 78.55 GB.
  admittedly this time if you round up to the nearest tenth, then 78.55
  → 78.6 so that makes sense but it doesn't apply to the above. this
  time it did take the max value with no complaining. the partition
  table reported 157.1 GB after resize.

  i didn't try 100% but i wonder if that would have actually worked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1067841/+subscriptions



More information about the foundations-bugs mailing list