topic Re: vgimport problem in Operating System - HP-UX

vgimport problem

Deepak Seth_1 — Wed, 02 Jul 2008 19:52:43 GMT

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.

Re: vgimport problem

Ivan Krastev — Wed, 02 Jul 2008 20:03:35 GMT

What error you have without -p flag ?

regards,
ivan

Re: vgimport problem

Deepak Seth_1 — Wed, 02 Jul 2008 20:05:56 GMT

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 .

Re: vgimport problem

Ivan Krastev — Wed, 02 Jul 2008 20:09:18 GMT

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

Re: vgimport problem

Deepak Seth_1 — Wed, 02 Jul 2008 20:11:36 GMT

see the attchment .

Re: vgimport problem

Deepak Seth_1 — Wed, 02 Jul 2008 20:16:38 GMT

no service guard . looks like i must be doing something really stupid.

Re: vgimport problem

Tim Nelson — Wed, 02 Jul 2008 20:29:40 GMT

need to run vgchid on the BCV volumes before import.

Re: vgimport problem

Deepak Seth_1 — Wed, 02 Jul 2008 20:41:31 GMT

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 .

Re: vgimport problem

Tim Nelson — Wed, 02 Jul 2008 20:50:55 GMT

>>(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 ??

Re: vgimport problem

Deepak Seth_1 — Wed, 02 Jul 2008 20:53:42 GMT

(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 .

Re: vgimport problem

Deepak Seth_1 — Wed, 02 Jul 2008 21:13:38 GMT

see some more strange behaviour
mv /etc/lvmatb /etc/lvmtab.orig
vgscan -a
it shows me that /dev/vgbaanpeu3 in lvmtab with one PV . That PV doesn't even belong that PV . i export the VG and imported again . But no luck . I see /dev/vgbaanpeu3 entry in lvmtab only when i do a vgscan and that too with just one PV.

Don't know what to do .

Re: vgimport problem

psreedhar — Thu, 03 Jul 2008 03:11:06 GMT

Hi,
I am sreedhar, i work closely with HPUX LVM product. Is it possible for you to send me the ouput of

./lvm.11 -l -d ,

I attached the lvm.11 command along with this.

I need to the output for all the disks.But that is quite lot of task. So could you please just send me as many as possible.

Without that output i have no other clue to solve this problem.

regards
sreedhar

Re: vgimport problem

Deepak Seth_1 — Thu, 03 Jul 2008 04:49:34 GMT

figure out the problem . i repeated the PV in the vgimport command . i wrote /dev/dsk/c11t3d2 twice . i fixed the second PV to /dev/dsk/c11t3d3 and vgimport worked fine .
Thanks for helping .

Re: vgimport problem

psreedhar — Thu, 03 Jul 2008 04:59:25 GMT

Hi,
Now i understood the whole reasoning.
LVM has logic to find duplicate disks even .
But it failed to do in your case. I need to debug the problem now.
can you tell me the exact details of the backend array you are using. Is it possible to give the setup for 10 mins to review the disks details.

regards
sreedhar

Re: vgimport problem

Deepak Seth_1 — Thu, 03 Jul 2008 05:13:37 GMT

the backend storage is EMC symmetrix , model 8530 . You just need the the output of the command u send me for all the PV's in questions.

Re: vgimport problem

psreedhar — Thu, 03 Jul 2008 07:33:45 GMT

I suspect some problem with LVM commands.
By the end of the day i will give you a C code, can you run that and give me the output.

Re: vgimport problem

psreedhar — Thu, 03 Jul 2008 08:42:05 GMT

Hi,

i attached both C code and the (IA)Binary along with this mail, if you have C compiler please build the code and run it using the following usage.

cc -o emc_inf emc_inq.c
./emc_inq ...

Can you send me the output for few of the disks in your list.
That will help me in debugging why LVM commands couldn't figure out the duplicate disks in the command line.

Re: vgimport problem

psreedhar — Thu, 03 Jul 2008 08:51:55 GMT

I couldnt attach C code earlier.

Re: vgimport problem

Sharma Sanjeev — Wed, 16 Jul 2008 10:56:08 GMT

Hi Deepak

Check your all disk belongs to same vgid
with
xd -j 8200 N 16 /dev/dsk.c?t?d?
and you can see the disks belongs to same or diffrent vgid

If it belongs to diffrent than you have to export your HORMCM Instance
and than you have to do pairrsync and pairsplit.
your problem will be resolved.

Regards
Sanjeev