Operating System - HP-UX
1748204 Members
3080 Online
108759 Solutions
New Discussion юеВ

VG not mounting custom_vg_activation() is set...

 
SOLVED
Go to solution
Reidmeister
Occasional Advisor

VG not mounting custom_vg_activation() is set...

I am having an issue with a VG not mounting during a reboot. The needs to manually be activated and mounted...

Here is my LVMRC file.


I have a vg that will not mount.
I have set AUTO_VG_ACTIVATE=0
and aslo have this setting for

custom_vg_activation()
{
/sbin/vgchange -a y -s vgora
parallel_vg_sync "/dev/vgora"

return 0
}

Does anything look wrong with this setting?
3 REPLIES 3
Torsten.
Acclaimed Contributor
Solution

Re: VG not mounting custom_vg_activation() is set...

If the VG is part of the cluster, then "-a y" won't work. This must be "-a e" or even "-a s" in this case. Have a look into the log for a related message.

BTW, why you use "-s"?

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Reidmeister
Occasional Advisor

Re: VG not mounting custom_vg_activation() is set...

Well rc.log just shows the command
minus the -s incidently...

As far why we are using the -s I cant say. I dont see any harm in it though. I think this command was chosen as it was documetend that way. I will experiment with your suggestions.

Also is there a another location I can look for more detail on the output from this file?
charlie_bulosan
Frequent Advisor

Re: VG not mounting custom_vg_activation() is set...

Hi,

This is part of the /etc/lvmrc of the adoptive node of my cluster and it activates the following VGs during reboot. These VGs are NOT part of a cluster's package(s).

------------------------------------
custom_vg_activation()
{
# e.g. /sbin/vgchange -a y -s
# parallel_vg_sync "/dev/vg00 /dev/vg01"
# parallel_vg_sync "/dev/vg02 /dev/vg03"
/sbin/vgchange -a y -s /dev/vg00
/sbin/vgchange -a y -s /dev/vg_RS2_01
/sbin/vgchange -a y -s /dev/vg_RT2_01
/sbin/vgchange -a y -s /dev/vg_RT2_02
/sbin/vgchange -a y -s /dev/vg_RT2_03
/sbin/vgchange -a y -s /dev/vg_RT1_APP
/sbin/vgchange -a y -s /dev/vg_PT101
/sbin/vgchange -a y -s /dev/vg_INTERFACE
/sbin/vgchange -a y -s /dev/vg_RT101
/sbin/vgchange -a y -s /dev/vg_RT102
/sbin/vgchange -a y -s /dev/vg_RD101
/sbin/vgchange -a y -s /dev/vg_RD102
parallel_vg_sync "/dev/vg00 /dev/vg_RS2_01 /dev/vg_RT2_01 /dev/vg_RT2_02 /dev/vg_RT2_03 \
/dev/vg_RT1_APP /dev/vg_PT101 /dev/vg_INTERFACE /dev/vg_RT101 /dev/vg_RT102 \
/dev/vg_RD101 /dev/vg_RD102"

return 0
}

-----------------------------------------

If the server in question is part of the node , it is recommended to set AUTO_VG_ACTIVATE to 0 and let the ServiceGuard package control file to activate the package volume group (which is usually vgchange -a e).


Regards,
Charlie