How can i update LVM after increase vdisk in eva3000

[Arturo_5]

Hello,

Yesterday i increased online the size of one vdisk in eva3000.
On the night i rebooted the machine for HPUX recognize the new size of the disk, now a need to use the new space creating a new lvol but LVM not recognize the size of the disk.

Ej:
from #diskinfo /dev/rdsk/c10t0d4
size= 240 GB
from #pvdisplay /dev/dsk/c10t0d4
size= 200 GB
from #vgdisplay -v vgpdb
size= 200 GB
and it is formed only for /dev/dsk/c10t0d4

Let me know your recomendations

[Steven E. Protter]

Try:

insf -C

followed by ioscan.

If the space is not recognized boot.

Depending on your interace you may be able to lvextend/fsadm (with OnlineJFS) without a boot.

Some disk arrays, Xiotech for example make it hard to do this. Adding dispace requires you to back up the logical volumes, then destroy, pvcreate (etc,) totally rebuild and restore.

I believe this desructive process is not needed on the eva3000 disk array.

SEP

[Sanjay_6]

Hi,

Checkout this link from itrc. You probably need to increase the MAX_PE per PV value while creating the vg to accomodate a large disk of that capacity.

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000063201757

The itrc doc id is KBRC00004285.

The doc also refers to some useful docs.

Hope this helps.

regds

[Alzhy · Accepted solution]

Arturo,

HP-UX does not have support for VDISK (aka LUN) expansion. Only Tru64 abd OpenVMS (the original intended environments for the EVA) support such.

So having not attempted to do such, it may actually result in corruption. You're lucky so far.

[Arturo_5]

Thanks folks for your ansewrs but let me clarify the scenario,

Actually HPUX know that the size of the disk (vdisk for EVA) was incresed, cause when i verify it, the command out result is the same from the change maded.

Nevertheless LVM don´t recognize the change, cause the command out result is accord to the old size of the disk.

Then from my point of view i need to actualize LVM configuration.

Have you any idea ?

[Patrick Wallek]

As far as I know what you want to do is not possible.

Diskinfo see's the correct size because it is reading the disk itself. LVM is seeing the size as it was when it was originally added to the VG.

LVM does not have the ability to extend the size of a disk. Once that disk is made part of a VG, you are stuck at that size.

The only way to get LVM to see the new size of the disk is to remove it from the VG and then try to add it back again.

[Patrick Wallek]

You would be better off adding a new LUN to the EVA and then just doing a vgextend to add it into the VG and then an lvextend to increase your LVs.

[Alzhy]

Full support for EVA VDISK expansion is not supported probaboy until HP-UX 11i v 3.0 - which will incorporate Tru64's features into HP-UX. Until then.. heed the advices you're getting - unless of course there are "tweaks" available (from HP?) which will allow you to tweak the system and actually force LVM to recognise the new size of the LUN.

[José Enrique González]

You could try exporting and re-importing the volume group that LUN is assigned to, and see what happens.

[Mark Grossman]

have to agree with Nelson and Patrick on this one - it cant be done (yet). We tried it when we first got the system.
Just add another vdisk and present it to the same host, and then extend your lvm and filesystem to it.

good luck,
Mark

[Shawn M Harris_1]

I was given an unsupported tool (vgmodify) that will increase the MAX_PE for a given PV. The VG associated with the PV would have to been deactivated. Try searching for the tool online but again it is unsupported.