From: Sunder Iyengar (Sunder.Iyengar@VERITAS.COM)
Date: Tue Apr 15 2003 - 18:58:58 EDT
Tried exportvg datavgc3?
If a VG was created on the second system on the same disks and vary'ed on,
then the disks would be reserved by that system. The first system would then
be unable to read the reserved disks and give the errors that you see.
Try,
# exportvg datavgc3
That will remove reference of the VG from first system.
Sunder.
-----Original Message-----
From: JackKramer@KYRUS.COM [mailto:JackKramer@KYRUS.COM]
Sent: Wednesday, 16 April 2003 8:32 AM
To: aix-l@Princeton.EDU
Subject: can't varyonvg
I know I made a mistake by varyoffvg, then creating a similar vg on a second
system with the same disks sharing the same ssa cabinet but now how to I
correct the problem?
I removed the vg from the second system successfully but I cannot remove the
vg on the first system without varying it on and I can't vary it on.
On the troubled system I have:
jack_as_root:># lspv hdisk56
0516-010 lspv: Volume group must be varied on; use varyonvg command.
PHYSICAL VOLUME: hdisk56 VOLUME GROUP: datavgc3
PV IDENTIFIER: 000c948d922d2754 VG IDENTIFIER 000c948d922d3042
PV STATE: ???????
STALE PARTITIONS: ??????? ALLOCATABLE: ???????
PP SIZE: ??????? LOGICAL VOLUMES: ???????
TOTAL PPs: ??????? VG DESCRIPTORS: ???????
FREE PPs: ???????
USED PPs: ???????
FREE DISTRIBUTION: ???????
USED DISTRIBUTION: ???????
Also:
jack_as_root:># varyonvg datavgc3
PV Status: hdisk56 000c948d922d2754 PVNOTINVG
hdisk62 000c947dcdff623b PVNOTINVG
hdisk63 000c948d922e42ed PVNOTINVG
0516-013 varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
I think I need to clear the descriptor area but how? A little help would be
appreciated.
What I initially wanted to do is move a vg from one system to another. I
think I need to export the vg after I varyoff. I will read up on what I am
trying to do but first I need to fix this.
Jack Kramer
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:45 EDT