[Linux-HA] HA EVMS start at boot

[Andreas Kurz]

On 1/24/07, Robert Wipfel <rawipfel at novell.com> wrote:
> >>> On Wed, Jan 24, 2007 at  2:21 PM, in message
> <904050d50701241321n7d41494ag8786077c67a22f92 at mail.gmail.com>, "Andreas Kurz"
> <andreas.kurz at gmail.com> wrote:
> > On 1/24/07, John Lange <john.lange at open- it.ca> wrote:
> >> I'm trying to get evms volumes to show up at boot time. SLES10 with
> >> heartbeat but I always get the following error:
> >>
> >> Starting EVMSEngine: The plug- in Novell- HA in
> >> module /lib/evms/2.5.5/hb2- 1.0.0.so failed to load.  The plug- in's
> >> setup_evms_plugin() function failed with error code 19: No such device.
> >>
> >> Yet, when I run "/etc/init.d/evms start" manually it starts no problem.
> >> I suspect heartbeat needs to be running and stabilized before
> >> evms_activate is called? Or is it a matter of adding evms resources to
> >> heartbeat or something along that line?
> >
> > Are you using the EvmsSCC OCF resource script in your configuration?
> > It's included in heartbeat 2.0.8. It should do exactly what you want:
> > evms_activate
>
> EvmsSCC is needed for making Shared (public) Cluster Containers (SCC) visible, as a dependency for hosting an OCFS2 cluster file systems over shared cluster segments, since EVMS' Cluster Segment Manager (CSM)  won't allow them to be activated until the node has joined the cluster. If you have logical volumes on local (or shared) disks, partitioned using GUID or DOS segment managers, then iirc boot.evms (which also calls evms_activate) should scan them in during boot (if chkconfig'd on). Changju will know for sure...

So for a private cluster container,  residing on a shared storage, the
evms_activate has to be run before heartbeat and the evms daemon is
started? This is enough to fail-over the private container in case of
a node failure?

Regards,
Andreas

>
> Hth,
> Robert
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>