Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Show physical location of VGDA

Status
Not open for further replies.

LuchoTB

MIS
Jan 20, 2003
38
ES
i want to change from BIG vg to a Scalable VG, and i have a lot of disk full.

how i show the physical location of VGDA ?, to free pp from the disk an change to scalable VG.





Saludos:
Lo mio no es el ingles (se nota)
 
I don't think that i totally understood your questionbut to be able to do this you will have to use chvg with the -G option

You need to have enough free space for this!


Code:
-G Changes the volume group to Scalable VG format. This can accommodate up to 1024 physical volumes and 4096 logical volumes. 
Notes:
The -G flag cannot be used if there are any stale physical partitions. 
Once the volume group is converted, it cannot be imported into AIX 5.2 or lower versions. 
The -G flag cannot be used if the volume group is varied on. 
There must be enough free partitions available on each physical volume for the VGDA expansion for this operation to be successful. 
Since the VGDA resides on the edge of the disk and it requires contiguous space for expansion, the free partitions are required on the edge of the disk. If those partitions are allocated for user usage, they will be migrated to other free partitions on the same disk. The rest of the physical partitions will be renumbered to reflect the loss of the partitions for VGDA usage. This will change the mappings of the logical to physical partitions in all the PVs of this VG. If you have saved the mappings of the LVs for a potential recovery operation, you should generate the maps again after the completion of the conversion operation. Also, if the backup of the VG is taken with the map option and you plan to restore using those maps, the restore operation may fail since the partition number may no longer exist (due to reduction). It is recommended that backup is taken before the conversion, and right after the conversion if the map option is utilized. 
Because the VGDA space has been increased substantially, every VGDA update operation (creating a logical volume, changing a log ical volume, adding a physical volume, and so on) may take considerably longer to run.

Regards,
Khalid
 
The VGDA is always at the very first blocks of a disk. If you go from VG to BIGVG, the VGDA on every disk increases in size and still needs to remain at the beginning of the disks, so the first partition of every disk needs to be free (or freeable by migrating that partition to some other place in the VG). After the VG is made BIGVG, the space that was previously the first partition on every disk is then used by the bigger VGDA and the remaining partitions will then be renumbered so that the partitions again start from 1 to NNN.

I've done that operation once, and it needed a free partition of 32MB on every disk.

Note that if you have a mirrored VG and have placed the mirrors on SAN LUNs in different SAN boxes (in different rooms), it may be wise to migrate the 1st partition away to a place of your choice beforehand, and not letting the chvg do that migrating stuff randomly.


HTH,

p5wizard
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top