vgimport problem

 
Deepak Seth_1
Regular Advisor

vgimport problem

trying to mount the EMC BCV devices to an HP host .
ll /dev/vgbaanpeu3/group
crw-r--r-- 1 root sys 64 0x060000 Jul 2 13:43 /dev/vgbaanpeu3/group
vgimport -p -v -m mapfile /dev/vgbaanpeu3

this works fine .
but when trying to do actually without the "p" flag , it just didn't import it .
(backup2 root):/users/dseth> sh 4pne
Beginning the import process on Volume Group "/dev/vgbaanpeu3".
this is what i get
vgimport: Warning: Volume Group belongs to different CPU ID.
Can not determine if Volume Group is in use on another system. Continuing.


--see below - this is what i get with "p" flag.
Beginning the import process on Volume Group "/dev/vgbaanpeu3".
vgimport: Warning: Volume Group belongs to different CPU ID.
Can not determine if Volume Group is in use on another system. Continuing.
Logical volume "/dev/vgbaanpeu3/lvol1" has been successfully created
with lv number 1.
Logical volume "/dev/vgbaanpeu3/lvol2" has been successfully created
with lv number 2.
Logical volume "/dev/vgbaanpeu3/lvol3" has been successfully created
with lv number 3.
Logical volume "/dev/vgbaanpeu3/lvol4" has been successfully created
with lv number 4.
Logical volume "/dev/vgbaanpeu3/lvol5" has been successfully created
with lv number 5.
Logical volume "/dev/vgbaanpeu3/lvol6" has been successfully created
with lv number 6.
Logical volume "/dev/vgbaanpeu3/lvol7" has been successfully created
with lv number 7.
Logical volume "/dev/vgbaanpeu3/lvol8" has been successfully created
with lv number 8.
Logical volume "/dev/vgbaanpeu3/lvol9" has been successfully created
with lv number 9.
Logical volume "/dev/vgbaanpeu3/lvol10" has been successfully created
with lv number 10.
Logical volume "/dev/vgbaanpeu3/lvol11" has been successfully created
with lv number 11.
Logical volume "/dev/vgbaanpeu3/lvol12" has been successfully created
with lv number 12.
Logical volume "/dev/vgbaanpeu3/lvol13" has been successfully created
with lv number 13.
Logical volume "/dev/vgbaanpeu3/lvol14" has been successfully created
with lv number 14.
Logical volume "/dev/vgbaanpeu3/lvol15" has been successfully created
with lv number 15.
Logical volume "/dev/vgbaanpeu3/lvol16" has been successfully created
with lv number 16.
Logical volume "/dev/vgbaanpeu3/lvol17" has been successfully created
with lv number 17.
Logical volume "/dev/vgbaanpeu3/lvol18" has been successfully created
with lv number 18.
Logical volume "/dev/vgbaanpeu3/lvol19" has been successfully created
with lv number 19.
Logical volume "/dev/vgbaanpeu3/lvol20" has been successfully created
with lv number 20.
Logical volume "/dev/vgbaanpeu3/lvol21" has been successfully created
with lv number 21.
Logical volume "/dev/vgbaanpeu3/lvol22" has been successfully created
with lv number 22.
Logical volume "/dev/vgbaanpeu3/lvol23" has been successfully created
with lv number 23.
Logical volume "/dev/vgbaanpeu3/lvol24" has been successfully created
with lv number 24.
Logical volume "/dev/vgbaanpeu3/lvol25" has been successfully created
with lv number 25.
Logical volume "/dev/vgbaanpeu3/lvol26" has been successfully created
with lv number 26.
Logical volume "/dev/vgbaanpeu3/lvol27" has been successfully created
with lv number 27.
Logical volume "/dev/vgbaanpeu3/lvol28" has been successfully created
with lv number 28.
Logical volume "/dev/vgbaanpeu3/lvol29" has been successfully created
with lv number 29.
Logical volume "/dev/vgbaanpeu3/lvol30" has been successfully created
with lv number 30.
Logical volume "/dev/vgbaanpeu3/lvol31" has been successfully created
with lv number 31.
Logical volume "/dev/vgbaanpeu3/lvol32" has been successfully created
with lv number 32.
Logical volume "/dev/vgbaanpeu3/lvol33" has been successfully created
with lv number 33.
Logical volume "/dev/vgbaanpeu3/lvol34" has been successfully created
with lv number 34.
Volume group "/dev/vgbaanpeu3" has been successfully created.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after activating the volume group.

never seen like this before that a preview works and non-preview didn't . any quick help is appreciated.
18 REPLIES 18
Ivan Krastev
Honored Contributor

Re: vgimport problem

What error you have without -p flag ?

regards,
ivan
Deepak Seth_1
Regular Advisor

Re: vgimport problem

Beginning the import process on Volume Group "/dev/vgbaanpeu3".
vgimport: Warning: Volume Group belongs to different CPU ID.
Can not determine if Volume Group is in use on another system. Continuing.

that's it . that is really strange .

Ivan Krastev
Honored Contributor

Re: vgimport problem

This message "Volume Group belongs to different CPU ID." is a warning.

Maybe this is group in ServiceGuard cluster.
After import - try to activate it read-only and check status.

regards,
ivan

Deepak Seth_1
Regular Advisor

Re: vgimport problem

see the attchment .
Deepak Seth_1
Regular Advisor

Re: vgimport problem

no service guard . looks like i must be doing something really stupid.
Tim Nelson
Honored Contributor

Re: vgimport problem

need to run vgchid on the BCV volumes before import.

Deepak Seth_1
Regular Advisor

Re: vgimport problem

vgchgid /dev/rdsk/c11t3d2 /dev/rdsk/c11t3d2 /dev/rdsk/c11t3d4 /dev/rdsk/c11t3d5 /dev/rdsk/c9t3d4 /dev/rdsk/c9t3d5 /dev/rdsk/c9t3d6
/dev/rdsk/c9t3d7 /dev/rdsk/c9t4d0 /dev/rdsk/c9t4d1 /dev/rdsk/c9t4d2 /dev/rdsk/c9t4d3 /dev/rdsk/c9t4d4 /dev/rdsk/c9t4d5 /dev/rdsk/c9
t4d6 /dev/rdsk/c9t4d7 /dev/rdsk/c11t3d1 /dev/rdsk/c9t5d0 /dev/rdsk/c11t2d3

no luck . on the messages has changed now to this .

(backup2 root):/users/dseth> sh 4pne
Beginning the import process on Volume Group "/dev/vgbaanpeu3".
(backup2 root):/users/dseth> vgchange -a y /dev/vgbaanpeu3
vgchange: Volume group "/dev/vgbaanpeu3" does not exist in the "/etc/lvmtab" file.

do i need to sync the standard and BCV's again .
Tim Nelson
Honored Contributor

Re: vgimport problem

>>(backup2 root):/users/dseth> sh 4pne
>>Beginning the import process on Volume >>Group "/dev/vgbaanpeu3".
>>(backup2 root):/users/dseth> vgchange -a y /dev/vgbaanpeu3

What is "sh 4pne" ? ( sorry if I missed this previously.)

I can only assume that the vgimport failed ( but no error messages shown).

What is being executed in 4pne ?

Can we just execute:
vgimport /dev/vgbaanpeu3... and see the error if any ?

the vgchid fixed the first error as origionally noted, now onto the second error if any ??

Deepak Seth_1
Regular Advisor

Re: vgimport problem

(backup2 root):/users/dseth> more 4pne
vgimport -v -m ~dseth/4pne.map /dev/vgbaanpeu3 /dev/dsk/c11t3d2 /dev/dsk/c11t3d2 /dev/dsk/c11t3d4 /dev/dsk/c11t3d5 /dev/dsk/c9t3d4 /
dev/dsk/c9t3d5 /dev/dsk/c9t3d6 /dev/dsk/c9t3d7 /dev/dsk/c9t4d0 /dev/dsk/c9t4d1 /dev/dsk/c9t4d2 /dev/dsk/c9t4d3 /dev/dsk/c9t4d4 /d
ev/dsk/c9t4d5 /dev/dsk/c9t4d6 /dev/dsk/c9t4d7 /dev/dsk/c11t3d1 /dev/dsk/c9t5d0 /dev/dsk/c11t2d3

this is just a file where i added my vgimport command with all the PV's .