Service Guard ( A.11.20.00.01 ) VG import fails on alternate node

anidil99 — Fri, 15 Mar 2013 20:12:29 GMT

All

I am having issue with VG export import on stanby node. My cluster is active active with Production package on primary and QA on seconday

I made some disk changes on the primary node for an oracle VG and trying to do vgexport and import on alternate node to sync up the configuration. However the vgimport is failing with error "physical volume XYZ already recorded in lvmtab_p file"

What is preventing the vgimport?

Primary node:

# /usr/sbin/vgexport -s -p -v -m /tmp/vgoradata.map.XXX vgoradata

( copied the map file to alternate node:/tmp/vgoradata.map.XXX )

Alternate node:

# vgexport /dev/vgoradata

# mkdir /dev/vgoradata

# mknod /dev/vgoradata/group c 128 0x0b5000

# vgimport -s -N -m /tmp/vgoradata.map.XXX vgoradata

vgimport: The physical volume "/dev/disk/disk126" is already recorded in the "/etc/lvmtab_p" file

I verified lvmtab_p and the disk 126 actually does not exist in it.

Is it possible that the lvmtab_p is corrupted on alternate node? If so, is it safe to re-create it by running vgscan -N command?

Please advice.

Thanks

Re: Service Guard ( A.11.20.00.01 ) VG import fails on alternate node

Ajin_1 — Tue, 26 Mar 2013 04:57:07 GMT

Follow the below steps ,if it wont work recreate the lvmtab

# /usr/sbin/vgexport -s -p -v -m /tmp/vgoradata.map.XXX vgoradata

( copied the map file to alternate node:/tmp/vgoradata.map.XXX )

Alternate node:

#vgexport -v /dev/vgoradata

# mkdir -m 755 /dev/vgoradata

# mknod /dev/vgoradata/group c 128 0x0b5000

# vgimport -s -m /tmp/vgoradata.map.XXX vgoradata

topic Service Guard ( A.11.20.00.01 ) VG import fails on alternate node in Operating System - HP-UX

Service Guard ( A.11.20.00.01 ) VG import fails on alternate node

Re: Service Guard ( A.11.20.00.01 ) VG import fails on alternate node