The following was filed automatically by anaconda: anaconda 11.5.0.38 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devicelibs/lvm.py", line 253, in vgcreate raise LVMError("vgcreate failed for %s" % vg_name) File "/usr/lib/anaconda/storage/devices.py", line 1655, in create lvm.vgcreate(self.name, pv_list, self.peSize) File "/usr/lib/anaconda/storage/deviceaction.py", line 206, in execute self.device.create(intf=intf) File "/usr/lib/anaconda/storage/devicetree.py", line 659, in processActions action.execute(intf=self.intf) File "/usr/lib/anaconda/storage/__init__.py", line 210, in doIt self.devicetree.processActions() File "/usr/lib/anaconda/packages.py", line 115, in turnOnFilesystems anaconda.id.storage.doIt() 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 1317, in nextClicked self.anaconda.dispatch.gotoNext() LVMError: vgcreate failed for vg_test1055
Created attachment 337055 [details] Attached traceback automatically from anaconda.
Created attachment 337056 [details] anaconda -rw-r--r-- root/root 83004 2009-03-27 15:29 tmp/anaconda.log -rw-r--r-- root/root 6562 2009-03-27 15:29 tmp/program.log -rw-r--r-- root/root 138581 2009-03-27 15:29 tmp/storage.log -rw-r--r-- root/root 33224 2009-03-27 15:33 tmp/syslog -rwxr-xr-x root/root 912 2009-03-27 15:10 tmp/vncserver.log
Seems like we are trying to add a PV to a VG that already has the PV :)
(In reply to comment #3) > Seems like we are trying to add a PV to a VG that already has the PV :) Scratch that. We are trying to add an already owned PV.
Running... ['lvm', 'vgremove', 'vg_test90'] /var/lock/lvm/V_vg_test90: flock failed: Resource temporarily unavailable Can't lock volume group vg_test90: skipping There is a case in vgremove that we don't handle.
The problem here is that somehow the lvm VG did not get removed properly. Anaconda gave the order to remove and lvm did not return an error, so anaconda went on its marry way assuming that the lvm VG was removed. This could be an lvm issue due to the fact that lvm does not return properly after an error.
Well, there is probably bug in return code for vgreduce if flock() call return EWOULDBLOCK. But, the main problem is why locking returns this code. I guess that there is another (not finished) lvm command running, which has VG locked. Isn't possible that anaconda run vgreduce in parallel with other command?
No, anaconda only does one lvm operation at a time. Reassigning on the basis of comments #6 and #7.
the vgremove return code is fixed in upstream cvs now, but it helps here only that the error is properly detected, so anaconda can fail properly :-) but the root cause why flock fail is still unknown...
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
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