Description of problem: pvmove fails with device-mapper error. The system with the problem was installed from scratch with a root LVM filesystem. After installation, an old LVM1 volume group (localvg1) was converted to LVM2 and imported into new volume group (localvg2). All volumes function properly other than the pvmove failing. The old volume group was created under RHEL v3WS. Version-Release number of selected component (if applicable): lvm2-2.00.21-2 kernel-2.6.8-1.528.2.10 How reproducible: Every time Steps to Reproduce: 1. Run pvmove 2. 3. Actual results: [root@rutabaga ~]# pvmove -v -n /dev/localvg2/home /dev/sda1 /dev/hda2 Finding volume group "localvg2" Archiving volume group "localvg2" metadata. Creating logical volume pvmove0 mirror: Required device-mapper target(s) not detected in your kernel [root@rutabaga ~]# Expected results: The move should succeed. Additional info:
You'll need to load the dm-mirror module into your kernel. Newest 'mkinitrd' see this done automatically at boot time. (See also bz #122991.)