Red Hat Bugzilla – Bug 138097
Remove PV from VG, VG has LV extents on it: attempts pvmove and fails
Last modified: 2009-04-16 19:10:48 EDT
Description of problem:
Create a VG and create an LV on top of it. Navigate to the PV under
the LV Physical View and click "Remove Volume from Volume Group".
After confirming that you really want to do this you get the error:
pvmove command failed. Command attempted: "/usr/sbin/pvmove /dev/sde1"
And this on the command line:
"mirror: Required device-mapper target(s) not detected in your kernel"
The pvmove command doesn't work directly from the command line either,
so this may not be a problem with the GUI. I'm probably have
something configured correctly, so this will probably end up notabug,
but I don't want to lose track of it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This error occurs when the devicemapper mirror target mod is not
present in the kernel. If running a 2.6.9 or greater kernel, 'modprobe
dm-mirror' should be run. To ensure the mod is loaded, run 'dmsetup
A method has been added to the command handler that calls 'dmsetup
targets' and returns TRUE or FALSE if the target is loaded in the
kernel. This method is called before 'pvmove' is called. If the target
is not present, the following error message is displayed:
"The dm-mirror module is either not loaded in your kernel, or your
kernel does not support the dm-mirror target. If it is supported, try
\'modprobe dm-mirror\'. Otherwise, operations that require moving data
on Physical Extents are unavailable."
I am marking this QA ready -- hoping this solution is satisfactory.
Available in 0.9.7-1.0
Without the dm-mirror target available I am now getting this traceback:
Traceback (most recent call last):
File "/usr/share/system-config-lvm/InputController.py", line 310, in
File "/usr/share/system-config-lvm/InputController.py", line 391, in
if alloc <= actual_free_extents:
NameError: global name 'actual_free_extents' is not defined
Same traceback whether the dm-mirror target is active or not.
Fixed in 0.9.9-1.0.
Verified in system-config-lvm-0.9.9-1.0. Man, pvmoves can take a
looooooooong time. May want to consider a "This will take awhile"
dialog. If so, that will be another item. Closing this one.