pvmove - Can't expand LV: Mirror support missing from kernel?

Hi,
I am having some trouble doing pvmove.

I did reduce the fs and resize the lv with these commands:
e2fsck -f /dev/mapper/vg00-data && resize2fs /dev/mapper/vg00-data 551000
lvresize -L 552000M /dev/vg00/data

So now pvdisplay says something like:

part    total   free    alloc
hdb1    1786    0       1786
hde1    1786    0       1786
hdf1    1786    0       1786
hdg1    2680    0       2680
hdh1    1190    603     587
sda1    3724    3724    0

Since I want to remove hdb1 and hde1 I tried to pvmove hdb1 with:
pvmove /dev/hdb1
My output follows:

thor:~# pvmove /dev/hdb1
  Can't expand LV: Mirror support missing from kernel?
  ABORTING: Temporary mirror activation failed.  Run pvmove --abort.
  device-mapper ioctl cmd 9 failed: Invalid argument
  Couldn't load device 'vg00-pvmove0'.
thor:~# pvmove --abort 
  Can't expand LV: Mirror support missing from kernel?
  Suspension of temporary mirror LV failed
  Can't expand LV: Mirror support missing from kernel?

I am running a clean 2.6.7-kernel, with device mapper, dm-crypt and raid (including all raidlevels) as modules, the only thing I do not have under RAID and LVM is Multipath I/O support.

Can anyone please tell me why I am getting this problem and how to solve it?

Do CC me, I am not subscribed to the list.

Thanks in advance

Magnus M�nsson <[email protected]>

Me too.

I'm afraid that the only response I've ever got to this is 'its not supported in LVM2'.

Some people have suggested using a kernel with the latest dm patches, which I tried and which failed.

About the only answer I have is to have enough spare disk to move everything over and remove the lv's residing on those pv's, reorganise them and then move everything back.

I think that the unpleasent answer here is that LVM2 is *not* ready for the enterprise user... sadly I've already deployed it.

[snip]

have

Yup, likewise; I was there about a month ago and it still doesn't work...

I strongly doubt that you'll get any help out of the list on this, but if someone does send you a fix which works, off-list, *please* send it to me too; I have two failing disks which I need to decommission.

Thanks!

(I'm hoping against hope that there really is a fix for this, and if theres anyone who would know, they'd be on this list. So if noone on this list comes up with a fix, I'd submit that LVM2 should absolutely NOT be used on production systems (until there *is* a fix: LVM is great in principle)).

stock 2.6 dosn't have many dm-targets in it. Pick up the LVM patches off the website and apply them for the more "experimental" things like mirroring.

--Dan

On Fri, Jul 02, 2004 at 07:41:54PM -0400, Dan Merillat alleged:

What the?

$ tar jtvf 2.6.7-udm1.tar.bz2 
drwxr-xr-x root/wheel        0 2004-07-01 13:45:46 2.6.7-udm1/
-rw-r--r-- root/wheel 14760862 2004-07-01 13:33:43 2.6.7-udm1/00001.patch
-rw-r--r-- root/wheel      372 2004-07-01 13:34:15 2.6.7-udm1/00002.patch
-rw-r--r-- root/wheel      825 2004-07-01 13:34:26 2.6.7-udm1/00003.patch
...

Some of those patch tarballs seem to be patching a whole lot more then just dm.

Garrick Staples, Linux/HPCC Administrator
University of Southern California

[snip]

Indeed and this is what I have in the .config for a kernel which can't do a pvmove;

CONFIG_BLK_DEV_DM=m
CONFIG_DM_CRYPT=m
CONFIG_DM_MULTIPATH=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
CONFIG_DM_FLAKEY=m
CONFIG_BLK_DEV_DM_BBR=m

oh and, yes, I did run modprobe dm-mirror.

What does 'dmsetup targets' return?
Does it include 'mirror' in the output list?
(And confirm what versions you're using: run 'lvm version')

Alasdair

[email protected]

# dmsetup targets
Unknown command
Usage:

dmsetup [--version] [-v|--verbose [-v|--verbose ...]]

        [-r|--readonly] [-j|--major <major>] [-m|--minor <minor>]

[snip]

So I got an updated version of dmsetup and now I get;

# dmsetup targets
mirror           v1.0.1
striped          v1.0.1
linear           v1.0.1
error            v1.0.1

but pvmove -tv /dev/hdf4 still fails with;

ABORTING: Temporary mirror activation failed.

does now
:)

# lvm version
  LVM version:     2.00.08 (2003-11-14)
  Library version: 1.00.07-ioctl (2003-11-21)
  Driver version:  4.1.0

That's test mode for you: it's continuing further into the pvmove than is possible when all writes are turned off (which is what test mode does) - it needs fixing to bail out sooner cleanly.

You really should update both of those.
Look at the current WHAT_NEW file to see how many fixed bugs you're running with!

Alasdair

[email protected]

So you are saying that its not really bad and I should run it without test mode and it will be ok?

Will do, thanks

You mean like dm-mirror?