Phil,

Don't agree.

If you have it on one system in the CONCURRENT VG, you have a
semi-corrupted situation. If the extendvg fails and the disk is only
av. on 1 side you have a prob. already. YOu should remove it from the
vg (reducvg off course) and then try it again from the other node (that
is what I meant with trying it again !) to avoid the 111111 sit.

Marcel

Phil Langerholc wrote:
> Bobohoolie wrote:
> > If you haven't: Try the extendvg from the other node !. Sometimes it
> > will work.
> > Otherwise: If you use Oracle and it is possble stop/start Oracle will
> > release some ' locking'
> >
> > Fix was needed for AIX 5.2 below ML 6. Not for 5.3 as far as I know.
> >
> > GoodLuck
> > pvb265 wrote:
> >
> >>>- I assume you user first cfgmgr -S
> >>
> >>done
> >>
> >>
> >>>- Use extendvg4vp for vpaths !
> >>
> >>the same error of extendvg.
> >>
> >>
> >>>- Create an PVID first on the disk to add
> >>>- Create the same PVID on the other node using the concurrent cluster
> >>>
> >>>Use on both nodes: chdev -l vpath1 -a pv=yes (vpath1, 2, 3 etc. off
> >>>course)
> >>>
> >>
> >>done soon after cfgmgr
> >>
> >>may I need of same AIX fix?
> >
> >
> Do an lquerypr -vh /dev/vpathx and see if there is a persistent reserve.
> If there is, do an lquerypr -ch /dev/vpathx and then run cfgmgr
> again and the PVID and vg assignment should come up. If you have added
> the disk to a vg on one system, I would not do an extendvg again from
> another server as you risk corrupting the VGDA on the drive.