The following was filed automatically by anaconda: anaconda 11.5.0.59 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devicelibs/lvm.py", line 410, in lvdeactivate raise LVMError("lvdeactivate failed for %s" % lv_name) File "/usr/lib/anaconda/storage/devices.py", line 2116, in teardown lvm.lvdeactivate(self.vg.name, self._name) File "/usr/lib/anaconda/storage/__init__.py", line 1069, in findExistingRootDevices device.teardown() File "/usr/lib/anaconda/upgrade.py", line 162, in findExistingRoots rootparts = findExistingRootDevices(anaconda, upgradeany=upgradeany) File "/usr/lib/anaconda/upgrade.py", line 136, in findRootParts anaconda.id.rootParts = findExistingRoots(anaconda) File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1339, in nextClicked self.anaconda.dispatch.gotoNext() LVMError: lvdeactivate failed for gfs2_lv
Created attachment 347872 [details] Attached traceback automatically from anaconda.
I am getting the same error (5) when I switch to VT2 and try to deactivate gfs2_lv. The error message is, "LV ipilcher_vg/gfs2_lv in use: not deactivating". I'm unable to tell exactly what is using the LV. gfs2_lv is actually a "virtual disk", containing a single partition (type 8e). It was part of a cluster of KVM or Xen guests (can't remember). Since there's no data on the LV, I'm going to blow it away and try again; I can recreate it if need be.
Created attachment 359093 [details] Attached traceback automatically from anaconda.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.