Volume group needs to be activated on reboot

[Big Ant]

Has anyone had the problem of having to activate a volume group every time the server reboots? I have a 100 gig Vdisks presented to my HPUX rx6600 server and on every reboot I have to reactivate the volume group

[Michal Kapalka (mikap) · Accepted solution]

hi,

check /etc/lvmrc if the activation of other vg's is activated.

mikap

[James R. Ferguson]

Hi:

That's interesting you should post in the ServiceGuard family...

Volume groups controlled by ServiceGuard are activated by the package control script governing them.

In the absence of ServiceGuard, the 'AUTO_VG_ACTIVATE=1' of '/etc/lvmrc' causes all volume groups to be activated at startup.

Otherwise, you can create a customized activation policy by modifying the 'custom_vg_activation()' function _and_ setting 'AUTO_VG_ACTIVATE=0' in '/etc/lvmrc'.

Overall, see the comments in '/etc/lvmrc'.

Regards!

...JRF...

[Big Ant]

Thanks allot. I checked the lvmrc file in etc and the Auto_VG_Activate was set to = 0.

[Mel Burslan]

Please make no mistake. If the volume group is the part of a serviceguard package, you should leave it as auto_vg_activate=0. If you have another VG that is not part of ANY cluster packages, you can then safely put this variable =1 for that VG

[Patrick Wallek]

>>auto_vg_activate=0. If you have another VG
>>that is not part of ANY cluster packages,
>>you can then safely put this variable =1 for
>>that VG

Not quite. The auto_vg_activate variable is applicable to **ALL** VGs.

If it is set to 1, then ALL VGs will be activated automatically.

If it is set to 0, NO VGs will be activated automatically. It is at this point that you have to set up manual VG activation, as described above AND in the file, for ALL VGs that need to be activated when the server boots. This includes VG00.

[Mel Burslan]

I am sorry. I think sleep deprivation is not a good thing. What I meant to say was you can activate those volume groups one by one as seen in the examples in the "custom_vg_activation()" block/function.

gotta get more caffeine infusion right about now.

[Sajjad Sahir]

Dear Friend

If the volume is groups is not activated then please check the /etc/lvmrc and set Auto_VG_Activate=1


thanks and regards

Sajjad Sahir

[Duncan Edmonstone]

I think the important point here is that *if* this is a serviceguard cluster, then whilst setting auto_vg_activate to 1 would appear to fix a problem with a local (non Serviceguard) VG not activating at boot, it will in fact BREAK your cluster - as others have pointed out, in a serviceguard cluster, any local VGs which are not part of a package should be started in the custom_vg_activation() function

HTH

Duncan