Bug 709033

Summary: LVMError: lvresize failed for lv_root: New size (59104 extents) matches existing size (59104 extents) Run `lvresize --help' for more information.
Product: [Fedora] Fedora Reporter: Pete Houston <rhbugz>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: anaconda_trace_hash:2114092e2a79637a60be4dc0bad720bdda7547223a1fed3bbf61e166d8ac7256
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 14:49:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Attached traceback automatically from anaconda. none

Description Pete Houston 2011-05-30 12:54:03 UTC
The following was filed automatically by anaconda:
anaconda 15.31 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicelibs/lvm.py", line 379, in lvresize
    raise LVMError("lvresize failed for %s: %s" % (lv_name, msg))
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 2548, in resize
    lvm.lvresize(self.vg.name, self._name, self.size)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 362, in execute
    self.device.resize(intf=intf)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 313, in processActions
    action.execute(intf=self.intf)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 356, in doIt
    self.devicetree.processActions()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/packages.py", line 116, in turnOnFilesystems
    anaconda.storage.doIt()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 211, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 130, in gotoNext
    self.moveStep()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1257, in nextClicked
    self.anaconda.dispatch.gotoNext()
LVMError: lvresize failed for lv_root:   New size (59104 extents) matches existing size (59104 extents)
  Run `lvresize --help' for more information.

Comment 1 Pete Houston 2011-05-30 12:54:13 UTC
Created attachment 501795 [details]
Attached traceback automatically from anaconda.

Comment 2 Pete Houston 2011-05-30 13:07:49 UTC
This error is triggered by creating logical volumes which together add up to more space than the available space in the volume group. This is allowed by the partition configuration system, but when the table is written to disk there is the error above.

My intention was to re-use an old volume group for this installation. The Group had 2 logical volumes, one of about 230GB and one of just 1GB (for swap). However, I'd prefer to rejig this for the new installation so wanted to break the bigger volume down into 2 volumes of about 50GB and leave the rest free.

Without deleting and adding, the only way to do this is to resize the big partition down to 50GB, add a new volume of 50GB, mark them both to be formatted and then assign them mount points (of / and /home in my case).

However, to format the resized partition the interface requires us to untick the resize box to then tick the format box (which is greyed out if resize is still ticked). This results in the partition being un-resized again and now I have a volume group of about 231GB with volumes of 230GB, 1GB and 50GB. This is clearly not going to work.

So, I think the bug is actually that the configurator allows the user to untick the resize box when doing so creates too much space for the volume group to cope with.

My workaround (and probably the correct way to do this) is to just delete the existing large volume and create 2 new ones.

Comment 3 Fedora End Of Life 2012-08-07 14:49:52 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping