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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Bad disk description stuck in VGDA - URGENT ! 1

Status
Not open for further replies.

MoshiachNow

IS-IT--Management
Feb 6, 2002
1,851
IL
Hi,This one is a bit tricky.
AIX 4.3.3. Had a mirrored rootvg,consisted of hdisk0 and hdisk5.
hdisk0 failed and was removed without unmirroring.
New hdisk0 was added with a different PVID.
Now all attempts all attempts to remove stale partitions fail :

redefinevg -d hdisk5 rootvg

synclvodm -Pv rootvg
0516-510 synclvodm: Physical volume not found for physical volume
identifier 004328daa95fc1400000000000000000.
0516-548 synclvodm: Partially successful with updating volume
group rootvg.
synclvodm: Logical volume hd5 updated.
synclvodm: Logical volume hd6 updated.
synclvodm: Logical volume hd8 updated.
synclvodm: Logical volume hd4 updated.
synclvodm: Logical volume hd2 updated.
synclvodm: Logical volume hd9var updated.
synclvodm: Logical volume hd3 updated.
synclvodm: Logical volume hd1 updated.

reducevg -d rootvg hdisk0
0516-022 lquerypv: Illegal parameter or structure value.
0516-022 lquerypv: Illegal parameter or structure value.
0516-884 reducevg: Unable to remove physical volume hdisk0.

because of the bad old hdisk0 PVID (004328daa95fc140) stuck in VGDA on the good hdisk5 :
lqueryvg -p hdisk5 -Atv
Max LVs: 256
PP Size: 24
Free PPs: 461
LV count: 15
PV count: 2
Total VGDAs: 2
Conc Allowed 0
MAX PPs per 1016
MAX PVs: 32
Conc Autovar 0
Varied on Co 0
Logical: 004328dac954a6e5.1 hd5 1
004328dac954a6e5.2 hd6 3
004328dac954a6e5.3 hd8 3
004328dac954a6e5.4 hd4 3
004328dac954a6e5.5 hd2 3
004328dac954a6e5.6 hd9var 3
004328dac954a6e5.7 hd3 3
004328dac954a6e5.8 hd1 3
004328dac954a6e5.9 scitexlv 3
004328dac954a6e5.10 scitemplv 3
004328dac954a6e5.11 psfontslv 3
004328dac954a6e5.12 scimarkerslv 3
004328dac954a6e5.13 scistoredblv 3
004328dac954a6e5.14 SharedItemslv 3
004328dac954a6e5.15 mngr_DBRoot 3
Physical: 004328daa95fc140 0 4
004328daa96db391 2 0
VGid: 004328dac954a6e5
Total PPs: 1084

Any advice ?



Long live king Moshiach !
 
try to remove the "old" disk using its PVID insted of hdisk0(old PVID)

reducevg -df VGname PVid

 
tried reducevg -df ,failed with error "hd6 must be closed ..".
But it's my paging space ....
More advice required,thanks

Long live king Moshiach !
 

So, you have removed disks which kept a copy (one of copies of hd6. Is it right? Now, when the disk is gone and replaced with new one, there are still informations that hd6 (one copy) resides on old disk (old PVID).

Maybe you should try to remove a zombie copy of hd6 (and not only hd6) from the configuration?

rmlvcopy hd6 1 OLD_DISK_PVID

If it would success then:

reducevg -df rootvg OLD_DISK_PVID


If not, then I have no clue.


r, m.
 
ogniemi,this was one great tip !

"reducevg -df rootvg OLD_DISK_PVID" worked like a miracle !
Thanks !

(the link above did not work)

Long live king Moshiach !
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top