1 LPAR called NodeA as primary node for PowerHA 6.1 on Site A.
1 LPAR called NodeB as secondary (cold) node for PowerHA 6.1 on SiteB.
1 Storage DS4700 on Site A.
1 Storage DS4700 on Site B.
All VIOS versions are 2.2.0.13-FP24 SP-03.
All AIX versions are 6.1.6.5.
Power version is 6.1 SP3.
Data VG is configured as LVM Cross Site, using one disk from each storage.
Both disks are configured with reserve_policy=no_reserve in all VIOS an LPARs.
queue_depth attribute is the same (10) in all VIOS and LPARs for this disks too.
My problem is that I can't increase the size of my data VG.
I increased the LUN size. Then I run cfgdev in both VIOS and cfgmgr in both LPARs. Also chvg -g datavg returns: "0516-1382 chvg: Volume group is not changed. None of the disks in the volume group have grown in size."
we have almost the same configuration on some clusters, resizing luns (storage DS8300) works without problems, I think even without cfgmgr on both vio and lpar, at least it's not necessary on the vio server
as gito said, dynamic resizing of hdisks that belong to a concurrent vg working in concurrent active or concurrent passive mode is not supported, so you need to at least bring the resource group down once
just could imagine the problem in conjunction with your ds4xxx storage and the drivers on the vio servers
we have clusters with 80+ concurrent pvs, imagine remapping of every single one (we have a script for this, but anyways..), that must be a bug, I would open an IBM ticket in your case
According to APAR IZ80021, there is an error on man pages of chvg -g. It says that since AIX 6.1 TL4 this is no longer a restriction.
I have all AIX and VIOS in TL6.
I presume this is a bug on VIOS side.
I've already opened a ticket on IBM support for a problem with a loss of a LUN access when a failover of DS controller occurs, but they don't have a solution yet.
-g
Will examine all the disks in the volume group to see if they have grown in size. If any disks have grown in size attempt to add additional PPs to PV. If necessary will determine proper 1016 multiplier and conversion to big
vg. Notes:
1 The user might be required to execute varyoffvg and then varyonvg on the volume group for LVM to see the size change on the disks.
2 There is no support for re-sizing while the volume group is activated in classic or enhanced concurrent mode.
3 There is no support for re-sizing for the rootvg.
if this is a bug, then it has made it's way even to aix 7.1
but I would call it lazy man page update policy then a bug