Cannot online or failover LVMVG resource
Article ID: 100021105
Updated On:
Resolution
Issue
Unable to
online or failover LVMVG resource.
Exact
error message
VCS WARNING
V-16-10011-10154 (sys_name) LVMVG:res_name:Online:Error retrieving pvid for
volume group vg_name
Details
The key to
resolving this issue is volume group (VG) should be imported on all nodes in the
cluster.
Here is the
high level procedure: This example shows a two node cluster.
1. Freeze
the service group.
2. Note down
a common major number to use on both nodes using "lvlstmajor" command. Same
major_number should be used in main.cf.
3. Go to the
node where manual import works. Import the VG on that node (say node
A)
# importvg
-V major_number -y vgname disk
4. Note down
the PVID &disks used on that node
# lspv |grep
vgname
second
column in the above list shows the PVID
5. Vary off
the VG. But do not export it.
# varyoffvg
vgname
"lspv"
should still show the PVID in second column
6. Manually
import the VG on the other node (node B).
# importvg
-V major_number -y vgname disk
If
successful go to step 11.
If it fails,
check the lspv output
#
lspv
Look for the
disks which carries the VG
If the
second column is shown as "nwn as "none" for these disks, then do the following
to fix it.
7. On this
node (node B) remove all disks belonging to the VG from ODM
# lsdev -Cc
disk > lsdev_disks.out1
# rmdev -dl
diskname
# lsdev -Cc
disk > lsdev_disks.out2
8. Now,
reinitialize the configuration so that all those deleted disks are re-read back
in.
#
cfgmgr
9. Now check
lspv again, the disks should show PVID on second column.
# lsdev -Cc
disk > lsdev_disks.out3
#
lspv
10. Import
the VG.
# importvg
-V major_number -y vgname disk
11. Vary off
the DG on this node (node B). But don't export it.
# varyoffvg
vgname
12. Unfreeze
the SG
13. Online
the SG on one node (A)
14. Switch
the SG to the other node (B)
15. Switch
back to this node (A)
Issue/Introduction
Cannot online or failover LVMVG resource
Was this article helpful?
Yes
No
Powered by
