[Pacemaker] stonith/SBD question in the event of a lost node

[mark - pacemaker list]

On Tue, Apr 3, 2012 at 5:09 AM, Lars Marowsky-Bree <lmb at suse.com> wrote:

> On 2012-04-02T11:01:31, mark - pacemaker list <m+pacemaker at nerdish.us>
> wrote:
>
> > Debian's corosync/pacemaker scripts don't include a way to start SBD, you
> > have to work up something on your own to get it started prior to
> corosync's
> > startup (from testing SBD with RHEL I seem to recall that its scripts
> will
> > start SBD for you, and that it has to be running before the other
> > components start).  I'm simply starting it as:  /usr/sbin/sbd -d
> > /dev/mapper/quorumdisk-sbd1 -W -D watch
> > ... prior to corosync running.  Does that seem reasonable?
>
> It's reasonable, but you've got to make sure that corosync doesn't get
> started if this fails.
>

OK, my startup script checks that sbd returns 0 and additionally checks
that it's running via pidof before starting corosync.


>
> And, of course, I assume that that LV is not actually managed by cLVM2
> or anything, and is shared between all the nodes etc.
>

Yes, it's actually just an iscsi volume shared by the nodes, the
/dev/mapper name is what it gets based on multipath.conf

I appreciate your help,
Mark




>
>
> Regards,
>    Lars
>
> --
> Architect Storage/HA
> SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix
> Imendörffer, HRB 21284 (AG Nürnberg)
> "Experience is the name everyone gives to their mistakes." -- Oscar Wilde
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120403/fda5a9a8/attachment.htm>