hdisk wrong PVID => importvg error

[alexia32]

Hello
I am trying to import some SAN disk VGs on a DR machine that contains the replication of the production env.

I was able to import properly 2 of the VG, but one of them is partially imported I get this error and I have one disk that can;t be recognise and even if it contains the data (I checked with lqueryvg and compare with the prod):

# importvg -y testvgdr hdisk2
0516-304 getlvodm: Unable to find device id 00ce212f1329b8fc in the Device
Configuration Database.
PV Status: hdisk2 00ce212f12e65297 PVACTIVE
hdisk4 00ce212f12e65320 PVACTIVE
hdisk5 00ce212f1329b872 PVACTIVE
hdisk6 00ce212f1329b984 PVACTIVE
hdisk7 00ce212f1329ba0e PVACTIVE
hdisk8 00ce212f132d6839 PVACTIVE
hdisk9 00ce212f132d68c1 PVACTIVE
hdisk10 00ce212f132d694f PVACTIVE
hdisk11 00ce5aff4f736c7b INVPVID
hdisk13 00ce212fbcaa3ea2 PVACTIVE
00ce212f1329b8fc NONAME
varyonvg: Volume group testvgdr is varied on.
testvgdr
PV Status: hdisk2 00ce212f12e65297 PVACTIVE
hdisk4 00ce212f12e65320 PVACTIVE
hdisk5 00ce212f1329b872 PVACTIVE
hdisk6 00ce212f1329b984 PVACTIVE
hdisk7 00ce212f1329ba0e PVACTIVE
hdisk8 00ce212f132d6839 PVACTIVE
hdisk9 00ce212f132d68c1 PVACTIVE
hdisk10 00ce212f132d694f PVACTIVE
hdisk13 00ce212fbcaa3ea2 PVACTIVE
00ce212f1329b8fc NONAME
varyonvg: Volume group testvgdr is varied on.
# lsvg -p testvgdr
testvgdr:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 399 0 00..00..00..00..00
hdisk4 active 399 0 00..00..00..00..00
hdisk5 active 399 0 00..00..00..00..00
0516-304 : Unable to find device id 00ce212f1329b8fc in the Device
Configuration Database.
00ce212f1329b8fc missing 399 0 00..00..00..00..00
hdisk6 active 399 0 00..00..00..00..00
hdisk7 active 399 0 00..00..00..00..00
hdisk8 active 399 0 00..00..00..00..00
hdisk9 active 399 0 00..00..00..00..00
hdisk10 active 399 0 00..00..00..00..00
hdisk13 active 399 1 00..00..00..00..01

# lsvg -l testvgdr
testvgdr:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
prodvg03lg1 jfs2log 1 1 1 closed/syncd N/A
0516-1147 : Warning - logical volume prodvg03l01 may be partially mirrored.
prodvg03l01 jfs2 300 300 11 closed/syncd /fsdata1
templv jfs2 100 100 3 closed/syncd /tempfs

Apparently hdisk11 has an incorrect PVID on the production the PVID corresponding to this replicated lun is: 00ce212fbcaa3dab

How can I replace the pvid by this one "00ce212fbcaa3dab" on the disk => I'm sure this could fix my first issue (Note: the NONAME PVID is a disk that the san team forget to replicate and will do it during the night)

Thanks for any help

Cheers
Al

 

[alexia32]

I get the second lun and have the same issue with PVID not corresponding.
#importvg -y testvgdr hdisk27
0516-304 getlvodm: Unable to find device id 00ce212fbcaa3dab in the Device
Configuration Database.
PV Status: hdisk2 00ce212f12e65297 PVACTIVE
hdisk3 00ce212f1329b8fc PVACTIVE
hdisk4 00ce212f12e65320 PVACTIVE
hdisk5 00ce212f1329b872 PVACTIVE
hdisk6 00ce212f1329b984 PVACTIVE
hdisk7 00ce212f1329ba0e PVACTIVE
hdisk8 00ce212f132d6839 PVACTIVE
hdisk9 00ce212f132d68c1 PVACTIVE
hdisk10 00ce212f132d694f PVACTIVE
hdisk11 00ce5aff4f736c7b INVPVID
hdisk13 00ce212fbcaa3ea2 PVACTIVE
hdisk27 00ce212f55d92439 INVPVID
varyonvg: Volume group testvgdr is varied on.
testvgdr

Apparently checking on history root user, I found out those commands have been run which could explain the pb on the ODM:
reducevg -d testvgdr 00ce212f168104d1
reducevg -d testvgdr 00ce212fbcaa3dab

So now I have an explanation, but need a solution to fix it as I still have the vg on error as doesn't contain all the data

Maybe so if it is possible to change the PVID of the disk in INVPVID and assign them the correct PVID.

Any idea if it is possible?

Cheers
Al

 

[victorv]

hi,
I am not able in this moment to give you a satisfactory answer; what I do in your case, is to use smitty vg,
and seeing all options that importvg permits.
Just a question:
how many disks composed the original vg (before do a exportvg) ?

bye
vic

 

[alexia32]

Hi

Well after investigation one disk was missing on the replication so the SAN team has done again the replication with all the disks and guess what I was able to import the vg without errors anymore!!!

Arg...!! never trusted SAN or network!!! ha ha ha


Cheers
Al