Change the Max PE for PV

[Qcheck]

How can I change Max PE for pv in HPUX? I tried to do this with vgmodify. Then it errored that the volume group named vgas is active.

So after unmounting the file systems, how come I can't deactivate the volume group? This is data volume group which is on SAN.

Thanks in advance.

[James R. Ferguson]

Hi:

Unmounting the filesystems in the volume group is just the first step to deactivating the volume group. You need to do:

# vgchange -a n /dev/vgNN

...then proceed with your 'vgmodify'. To reactivate the volume group, do:

# vgchange -a y /dev/vgNN

Regards!

...JRF...

[Tim Nelson]

I assume you are reading all the instructions in the vgmodify man page, you may still have more steps to move the first extent to make room for the new map info then renumbering the extents.


Hope you have a fresh backup in case something fails.

[Qcheck]

Thank you James. Now I can deactivate. But when I tried to modify like following:

vgmodify -e 16500 -n /dev/vgas, I got the following:

Vgmodify: This operation can only be completed if PE number zero on /dev/rdsk/c13t0d1" is free.

[Torsten.]

You need to run 11.23 to do this.

A new version (I don't remember details at the moment) can do this online. Have to check this ...

With 11.31 you may consider to use LVM version 2.0 or version 2.1 - this works different ...

[James R. Ferguson]

Hi (again):

> Vgmodify: This operation can only be completed if PE number zero on /dev/rdsk/c13t0d1" is free.

You need to use 'pvmove' to free the first extent. See:

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

Regards!

...JRF...

[Steven E. Protter]

Shalom,

This is set on the volume group level.

It can not be changed except in HP-UX 11.31

You need on other versions of the OS to vgexport the volume group and recreate the volume group with less physical volumes -p or -s parameter.

SEP

[Patrick Wallek]

SEP,

Actually that isn't true. The vgchange command is available in HP-UX 11.23.

[Tim Nelson]

vgmodify was introduced into 11.23 around Feb 2007 with patch PHCO_35524

[Qcheck]

I did pvmove and vgmodify. Everything worked that Max PE changed as what I wanted, except after mounting the file systems, I lost data(don't worry only test server, thats the reason I was testing).

what is the command to restore? I have the backup on ignite server. The server I am working is ignite client.... :-(

[Qcheck]

Sorry, after vgmodify, I couldn't mount the filesystems. Am I missing any other step prior to mount the file systems?

[James R. Ferguson · Accepted solution]

Hi (again):

> Sorry, after vgmodify, I couldn't mount the filesystems. Am I missing any other step prior to mount the file systems?

Did you do (?):

# vgchange -a y /dev/vgNN

Regards!

...JRF...

[Qcheck]

Sorry James, Got me....my bad, I thought I did, but apparently not when I checked now, thats the reason I couldn't mount. So stupid.

I think time to go home. I am working on too many things at the same(moving apps to prod) and working from morning 7:30am EST.

I appreciate your time James..

Thanks again everyone..

[HCL123]

Pratibha

Umounting the filesystems in the volume group is just the first step to deactivating the volume group. You need to do:

# vgchange -a n /dev/vgNN
then use vgextend and modify vg

# vgchange -a y /dev/vgNN

Regards

shelendra shukla

[Torsten.]

What hp-ux release are you using?


New for 11.31 september release:

The vgmodify command supports LUN expansion on a Version 1.0 volume group **without** deactivating the volume group.

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

[Qcheck]

Torsten, I am running 11.23 version

[James R. Ferguson]

Hi:

> Shelendra: Umounting the filesystems in the volume group is just the first step to deactivating the volume group. You need to do:

COPYING, VERBATIM my opening comment a DAY LATER IS BLATANT PLAGARISM. You added nothing to this thread other than a clear attempt to garner points for yourself.


Pratibha, it is always helpful (and wise) to specify your OS release in posts of this nature. It was clear to me that you were running either 11.31 or 11.23 with the 'vgmodify' patch, but adding the release level would have been very useful, particularly in light of Torsten's last pointer for 11.31.

...JRF...

[Qcheck]

I know, I should have mentioned the version. However everything worked. Thanks James.