pvmove error

[Anand Sreenivasan]

I am doing a PVMOVE from one disk to another in a volumegroup and I am getting this error. Please do remember that I have a logical volume inside this volumegroup which is stripped across 5 disks. I have 3 more logical volumes which are not stripped and these are the ones I am trying to consolidation by PVMOVE. I am not moving these to the disks used by the stripped LV. Thanks for any help.

# pvmove /dev/dsk/c11t12d0 /dev/dsk/c11t2d5
Device file path "/dev/dsk/c11t12d0" is an alternate path
to the Physical Volume. Using Primary Link "/dev/dsk/c9t8d1".
Operation cannot be performed because some of the data on the physical volume
is striped and striped mirroring is not supported. To enable data transfer for
a physical volume through mirroring/reduction, do not specify the striping
options (-i, -I) when creating logical volumes on that physical volume.

[Kent Ostby]

I'd do a pvdisplay on /dev/dsk/c11t12d0.

What this error message means is that this disk contains at least some striped lvols.

Since there are striped lvols, pvmove wont work.

See the man page for lvcreate for details.

[Anand Sreenivasan]

I did and there only 3 extents being used in this PV and that this is not striped. Ay more ideas...

[Kent Ostby]

Can you post pvdisplay data for the two disks in question and lvdisplay data for any lvols that reside on them ?

That might give us some ideas.

[Mitra Rath]

Hi anand,
Kent is right,if there is any striped lvols in that disk it won`t go for a pvmove......And what is that error for alternate disk....why are u not using the primary diak path for command...

Mitra

[Anand Sreenivasan]

Here is the output for those 2 PV's in question and the LV which I am trying to move..
pvdisplay /dev/dsk/c11t12d0
Device file path "/dev/dsk/c11t12d0" is an alternate path
to the Physical Volume. Using Primary Link "/dev/dsk/c9t8d1".
--- Physical volumes ---
PV Name /dev/dsk/c9t8d1
PV Name /dev/dsk/c11t12d0 Alternate Link
VG Name /dev/vg04
PV Status available
Allocatable yes
VGDA 2
Cur LV 1
PE Size (Mbytes) 4
Total PE 2157
Free PE 2154
Allocated PE 3
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On

pvdisplay /dev/dsk/c11t2d5
--- Physical volumes ---
PV Name /dev/dsk/c11t2d5
PV Name /dev/dsk/c9t2d5 Alternate Link
VG Name /dev/vg04
PV Status available
Allocatable yes
VGDA 2
Cur LV 1
PE Size (Mbytes) 4
Total PE 2157
Free PE 1000
Allocated PE 1157
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On

lvdisplay /dev/vg04/utl_filelv
--- Logical volumes ---
LV Name /dev/vg04/utl_filelv
VG Name /dev/vg04
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 12
Current LE 3
Allocated PE 3
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

I tried using the alternate link since I thought that might be the issue. It was not that though....

[Fred Ruffet]

Is there some lv wich are mirrored on source or dest PV ? Same question for destination PV ?

Regards,

Fred

[Anand Sreenivasan]

Nope, I use hardware mirroring and noone of the logical volumes is mirrored software wise.

[Fred Ruffet]

Isn't there LV extends from a LV you move already on the destination PV ?

What if you use directly primary path ?

Regards,

Fred

[Anand Sreenivasan]

I used both Primary and Alternate paths and I am getting the same error which I have posted. I do not know where do I go from here ...

[RolandH]

As said before you are not able to to a pvmove if some striped lvols located on the sam pv, too.

The solution is to create a new lv on the new pv and just copy your data to the new lv.

# lvcreate /dev/vg04
Omit the -l or -L option. This will produce a lv with zero lengh.
# lvextend -L 12 /dev/vg04/
Produce a Lvol with 12MB space.
# newfs -F vxfs /dev/vg04/
# mkdir /tmp_lvol
# mount /dev/vg04/ /tmp_lvol
# cd
# tar cf - . | (cd /tmp_lvol; tar xf - )
Now unmount your old lvol and change the /etc/fstab that you new lvol is mounted to your original mount point.
After you have checked that everthing is ok, you can remove your old lvol.

Roland

[RolandH]

I made a littel mistake. The lvextend must be this.

# lvextend -L 12 /dev/vg04/ /dev/dsk/c11t2d5

Roland

[Patrick Wallek]

What if you put the LV name in your pvmove command.

# pvmove -n /dev/vg??/lvol? /dev/dsk/c11t12d0 /dev/dsk/c11t2d5

This allows you to move a specific LV from one disk to another. Try that and see what happens.

[Anand Sreenivasan]

I dont want to create a seperate filesystem for this. The whole idea behind this was to get some disks back. Anyways I am going to go with the suggestion of naming the logical volume when I use PVMOVE. I will keep you all informed. Thanks for the help...