vgmodify help

[mjos]

I just read the man pages for pvmove

"pvmove cannot be performed if the volume group is activated in shared
mode."

This VG in question is clustered across two nodes & has LUNs from an external storage presented to two nodes. Currently the VG is active only on the primary node with the secondary node acting as failover. In this scenario, will the pvmove command work on the primary node, since the LUNs are shared across both the nodes.

[James R. Ferguson]

Hi (again):

> Currently the VG is active only on the primary node with the secondary node acting as failover.

Then the volume group isn't in "shared" mode. Shared means that it is active for read/write on both nodes. See the 'lvchange(1M)' manpages.

Regards!

...JRF...

[Benoy Daniel]

Online vgmodify is only supported in LVM2 and not in LVM1.

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01920387/c01920387.pdf (BSC link updated by admin)

[Torsten.]

See page 14 - online examples for LVM 1.0.

[Torsten.]

VG is LVM version 1:

# pvmove /dev/dsk/c3t0d1:0 /dev/dsk/c3t0d1
pvmove: The volume group "/dev/vg01" is not active. Only an active
volume group can be extended.

# vgchange -a y vg01
Activated volume group
Volume group "vg01" has been successfully changed.


# pvmove /dev/dsk/c3t0d1:0 /dev/dsk/c3t0d1
Transferring logical extents of logical volume "/dev/vg01/lvol1"...
Physical volume "/dev/dsk/c3t0d1" has been successfully moved.
Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.con
f

[mjos]

When I do a pvmove, it gives me the below error -

#pvmove /dev/disk/disk2909:0 /dev/disk/disk2909
pvmove: Not enough free physical extents available.
Logical volume "/dev/orvg_db01/lvdat01" could not be extended.
pvmove: Cannot find a free physical extent for logical extent 0
of logical volume "/dev/orvg_db01/lvdat01".

#vgdisplay orvg_db01
--- Volume groups ---
VG Name /dev/orvg_db01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 5
Open LV 5
Max PV 16
Cur PV 3
Act PV 3
Max PE per PV 1023
VGDA 6
PE Size (Mbytes) 32
Total PE 2557
Alloc PE 2206
Free PE 351
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

I need to free up the first extent on all the below luns

Physical Extent zero is not free on all PVs. You will not achieve these
values until the first extent is made free (see pvmove(1M)) on all the
following disks:
/dev/rdisk/disk2909
/dev/rdisk/disk2913
/dev/rdisk/disk4684

[Torsten.]

If you already have 3 PVs, why not simply add a fourth?

[mjos]

Well, here I want to increase the MAX PV to 255 & MAX_PE to 15868. This is a different VG and not the first one which I specified. This VG is not in Prod so I thought to test the vgmodify here.

[Torsten.]

Increasing the MAX values should work anyway, I think.

[mjos]

Thanks, I think it should work but now I am running into a different issue. Vgmodify is not taking the -a switch for doing it in online mode

#vgmodify -a -p 24 -e 4348 orvg_db01
Usage: vgmodify
[-e MaxPhysicalExtents]
[-p MaxPhysicalVolumes]
[-l MaxLogicalVolumes]
[-v]
[-n]
[-r]
[-B bootable]
VolumeGroupName {[pv_path] [pv_path] ....}

or vgmodify -o [-v] [-r] [-B bootable] VolumeGroupName {[pv_path] ....}

or vgmodify -t [-v] [-n] [-B bootable] VolumeGroupName {[pv_path] ....}
"a": Illegal option.
#vgmodify -p 24 -e 4348 orvg_db01
vgmodify: The volume group "orvg_db01" is active on this system.
Cannot perform requested change.