vg and lv extend errors

[Joe Arruda]

I am trying to add space to to volume groups and LV's
extend errors ??
# vgdisplay -v vg03_backup
--- Volume groups ---
VG Name /dev/vg03_backup
VG Write Access read/write
VG Status available
Max LV 126
Cur LV 1
Open LV 1
Max PV 8
Cur PV 3
Act PV 3
Max PE per PV 51199
VGDA 6
PE Size (Mbytes) 4
Total PE 69117
Alloc PE 65535
Free PE 3582
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 1638368m
VG Max Extents 409592

--- Logical volumes ---
LV Name /dev/vg03_backup/backup
LV Status available/syncd
LV Size (Mbytes) 262140
Current LE 65535
Allocated PE 65535
Used PV 3


--- Physical volumes ---
PV Name /dev/dsk/c4t0d4
PV Name /dev/dsk/c8t0d4 Alternate Link
PV Name /dev/dsk/c6t0d4 Alternate Link
PV Name /dev/dsk/c2t0d4 Alternate Link
PV Status available
Total PE 51199
Free PE 0
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c8t0d6
PV Name /dev/dsk/c4t0d6 Alternate Link
PV Name /dev/dsk/c6t0d6 Alternate Link
PV Name /dev/dsk/c2t0d6 Alternate Link
PV Status available
Total PE 12799
Free PE 0
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c6t0d5
PV Name /dev/dsk/c8t0d5 Alternate Link
PV Name /dev/dsk/c2t0d5 Alternate Link
PV Name /dev/dsk/c4t0d5 Alternate Link
PV Status available
Total PE 5119
Free PE 3582
Autoswitch On
Proactive Polling On


#

[Uday_S_Ankolekar]

You have enough free extents. You can use lvextend to increase file system

What kind of errors you see?

[James R. Ferguson]

Hi:

You don't offer what commands are failing. However, '/dev/vg03_backup/backup' has the maximum number of extents that are supported for a version 1.0 volume group already allocated: 65,535.

Regards!

...JRF...

[Joe Arruda]

ussing sam web page

Status: Running Completed Error Killing Killed
Name: Extend LV: /dev/vg03_backup/backup
Running Command: /usr/sbin/lvextend -A y -l 275456 /dev/vg03_backup/backup &&
/usr/sbin/umount /dev/vg03_backup/backup &&
/usr/sbin/extendfs -F vxfs /dev/vg03_backup/rbackup &&
/usr/sbin/mount -F vxfs -o ioerror=mwdisable,delaylog,nodatainlog,dev=40030001 /
dev/vg03_backup/backup /u03

[James R. Ferguson]

Hi (again):

> ussing sam web page

This matters not. As I said, you have already allocated the maximum number of extents allowed for a LVM 1.0 format volume group.

To see the limits, do:

# lvmadm -t

Regards!

...JRF...

[Joe Arruda]

Thanks
can you suggest any options ??

[Tim D Fulford]

You have very few options..

- backup data in vg03
- destroy vg & recreate with a larger PE (Physical Extent size)
- #vgcreate -s 8 vg03_backup /dev/dsk/.......
- lvcreate the relevant LV's
- format the LVs (as required newfs etc)
- mount them
- restore data from backup....

Tim

[Joe Arruda]

Thanks
I will try first one

[James R. Ferguson]

Hi (again):

> can you suggest any options ??

Depending on the update release of 11iv3 you are running, you have the 'vgversion' command that enables in-place volume group migration from version 1.0 to version 2.x.

http://docs.hp.com/en/5992-6592/vgversion-wp.pdf

Regards!

...JRF...

[Joe Arruda]

Thanks I might be out of luck

Currently the server has 11.31 March 2008, and according to the vgmodify documentation it does not accomplish with the minimum OS version necessary to use the proposed procedures to increase a LUN: