Red Hat Bugzilla – Bug 496181
LVMError in lvactivate
Last modified: 2009-04-21 21:13:41 EDT
The following was filed automatically by anaconda:
anaconda None exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/storage/devicelibs/lvm.py", line 397, in lvactivate
raise LVMError("lvactivate failed for %s" % lv_name)
File "/usr/lib/anaconda/storage/devices.py", line 1960, in setup
File "/usr/lib/anaconda/storage/devices.py", line 584, in minSize
File "/usr/lib/anaconda/iw/partition_ui_helpers_gui.py", line 383, in createPreExistFSOptionSection
reqlower = origrequest.minSize
File "/usr/lib/anaconda/iw/lvm_dialog_gui.py", line 491, in editLogicalVolume
(row, self.fsoptionsDict) = createPreExistFSOptionSection(reallv, maintable, row, mountCombo, self.storage, ignorefs = ["mdmember", "lvmpv", "vfat"], luksdev=templuks)
File "/usr/lib/anaconda/iw/lvm_dialog_gui.py", line 716, in editCurrentLogicalVolume
File "/usr/lib/anaconda/iw/lvm_dialog_gui.py", line 747, in editLogicalVolumeCB
LVMError: lvactivate failed for lv_root
Created attachment 339956 [details]
Attached traceback automatically from anaconda.
This may be a duplicate of Bug 495848, but I am no expert. I was testing whether that bug could also be recreated from the F11 Spin1 LiveCD. The exception occurred at the exact same step in the process as it did in the referenced bug, but I noticed that the tracebacks were different. Anyway, here is the general process to reproduce this bug.
1. Install F11 beta, and check the "Encrypt Disk" option.
2. After successful install, boot from Spin1 LiveCD (we're going to install again).
3. Start install from LiveCD. Make sure you enter the passphrase for the encrypted drive.
4. When you get to drive layout, select "Create Custom layout" and click "Next"
5. Select /dev/sda2 and click "Edit". (This should be the device holding the current LVM)
6. Click the "Format as:" box, and choose "physical volume (LVM)". The
"Encrypt" checkbox should already be checked. Leave it that way, and click
7. Under the volume group, select "lv_root" then click "Edit".
8. When the "Edit LVM Volume Group" window pops up, select "lv_root" and click
Excpected behavior: At step #5, a dialogue box should have popped up stating that you couldn't edit that device because it was part of a volume group. This is what happens when drive was not previously encrypted.
Actual behavior: At step #5, it lets you edit and format /dev/sda2. These results in the exception being thrown after step 8.
I just tried the boot.iso from the nightly build for 4-20-2009. This bug is fixed as of anaconda 220.127.116.11-1, thanks!