Page MenuHomeClusterLabs Projects
Files F3154872

No OneTemporary
Actions

View Options

diff --git a/Makefile.am b/Makefile.am
index ade9076..2141f88 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -1 +1 @@
-SUBDIRS = src agent
+SUBDIRS = src agent man
diff --git a/configure.ac b/configure.ac
index c654a9c..a1edb59 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1,57 +1,57 @@
dnl
dnl autoconf for Agents
dnl
dnl License: GNU General Public License (GPL)
dnl ===============================================
dnl Bootstrap
dnl ===============================================
AC_PREREQ(2.63)
dnl Suggested structure:
dnl information on the package
dnl checks for programs
dnl checks for libraries
dnl checks for header files
dnl checks for types
dnl checks for structures
dnl checks for compiler characteristics
dnl checks for library functions
dnl checks for system services
AC_INIT([sbd],
- [0.0.1],
+ [1.0],
[lmb@suse.com])
AC_CANONICAL_HOST
AC_CONFIG_AUX_DIR(.)
AC_CONFIG_HEADERS(config.h)
AM_INIT_AUTOMAKE
AM_PROG_CC_C_O
PKG_CHECK_MODULES(glib, [glib-2.0])
PKG_CHECK_MODULES(libcoroipcc, [libcoroipcc])
PKG_CHECK_MODULES(pcmk, [pcmk, pcmk-cib])
PKG_CHECK_MODULES(libxml, [libxml-2.0])
dnl checks for libraries
AC_CHECK_LIB(aio, io_setup, , missing="yes")
AC_CHECK_LIB(plumbgpl, init_set_proc_title, , missing="yes")
AC_CHECK_LIB(crmcommon, set_crm_log_level, , missing="yes")
AC_CHECK_LIB(cib, cib_new, , missing="yes")
AC_CHECK_LIB(pe_status, pe_find_node, , missing="yes")
AC_CHECK_LIB(pe_rules, test_rule, , missing="yes")
AC_CHECK_LIB(crmcluster, crm_peer_init, , missing="yes")
if test "$missing" = "yes"; then
AC_MSG_ERROR([Missing required libraries or functions.])
fi
dnl The Makefiles and shell scripts we output
-AC_CONFIG_FILES([Makefile src/Makefile agent/Makefile])
+AC_CONFIG_FILES([Makefile src/Makefile agent/Makefile man/Makefile])
dnl Now process the entire list of files added by previous
dnl calls to AC_CONFIG_FILES()
AC_OUTPUT()
diff --git a/man/Makefile.am b/man/Makefile.am
new file mode 100644
index 0000000..6e2684d
--- /dev/null
+++ b/man/Makefile.am
@@ -0,0 +1,4 @@
+man_MANS = sbd.7 sbd.8
+
+EXTRA_DIST = $(man_MANS)
+
diff --git a/man/sbd.7 b/man/sbd.7
new file mode 100644
index 0000000..100c05c
--- /dev/null
+++ b/man/sbd.7
@@ -0,0 +1,326 @@
+.TH sbd 7 "29 Mar 2012" "" "cluster-glue"
+.\"
+.SH NAME
+sbd \- Stonith Block Device
+.\"
+.SH DESCRIPTION
+.br
+\fB* Data Protection\fR
+
+The SLE HA cluster stack's highest priority is protecting the integrity
+of data. This is achieved by preventing uncoordinated concurrent access
+to data storage - such as mounting an ext3 file system more than once in
+the cluster, but also preventing OCFS2 from being mounted if
+coordination with other cluster nodes is not available. In a
+well-functioning cluster, Pacemaker will detect if resources are active
+beyond their concurrency limits and initiate recovery; further, its
+policy engine will never exceed these limitations.
+
+However, network partitioning or software malfunction could potentially
+cause scenarios where several coordinators are elected. If this
+so-called split brain scenario were allowed to unfold, data corruption
+might occur. Hence, several layers of protection have been added to the
+cluster stack to mitigate this.
+
+IO fencing/STONITH is the primary component contributing to this goal,
+since they ensure that, prior to storage activation, all other access is
+terminated; cLVM2 exclusive activation or OCFS2 file locking support are
+other mechanisms, protecting against administrative or application
+faults. Combined appropriately for your setup, these can reliably
+prevent split-brain scenarios from causing harm.
+
+This chapter describes an IO fencing mechanism that leverages the
+storage itself, following by a description of an additional layer of
+protection to ensure exclusive storage access. These two mechanisms can
+even be combined for higher levels of protection.
+.\"
+.P
+\fB* Storage-based Fencing\fR
+
+In scenarios where shared storage is used one can
+leverage said shared storage for very reliable I/O fencing and avoidance
+of split-brain scenarios.
+
+This mechanism has been used successfully with the Novell Cluster Suite
+and is also available in a similar fashion for the SLE HA 11 product
+using the "external/sbd" STONITH agent.
+
+In an environment where all nodes have access to shared storage, a small
+partition is formated for use with SBD. The sbd daemon, once
+configured, is brought online on each node before the rest of the
+cluster stack is started, and terminated only after all other cluster
+components have been shut down - ensuring that cluster resources are
+never activated without SBD supervision.
+
+The daemon automatically allocates one of the message slots on the
+partition to itself, and constantly monitors it for messages to itself.
+Upon receipt of a message, the daemon immediately complies with the
+request, such as initiating a power-off or reboot cycle for fencing.
+
+The daemon also constantly monitors connectivity to the storage device,
+and commits suicide in case the partition becomes unreachable,
+guaranteeing that it is not disconnected from fencing message. (If the
+cluster data resides on the same logical unit in a different partition,
+this is not an additional point of failure; the work-load would
+terminate anyway if the storage connectivity was lost.)
+
+SBD supports one, two, or three devices. This affects the operation
+of SBD as follows:
+
+.B ** One device
+
+In its most simple implementation, you use one device only. (Older
+versions of SBD did not support more.) This is appropriate for clusters
+where all your data is on the same shared storage (with internal redundancy)
+anyway; the SBD device does not introduce an additional single point of
+failure then.
+
+If the SBD device is not accessible, the daemon will fail to start and
+inhibit openais startup.
+
+.B ** Two devices
+
+This configuration is a trade-off, primarily aimed at environments where
+host-based mirroring is used, but no third storage device is available.
+
+SBD will not commit suicide if it loses access to one mirror leg; this
+allows the cluster to continue to function even in the face of one outage.
+
+However, SBD will not fence the other side while only one mirror leg is
+available, since it does not have enough knowledge to detect an asymmetric
+split of the storage. So it will not be able to automatically tolerate a
+second failure while one of the storage arrays is down. (Though you
+can use the appropriate crm command to acknowledge the fence manually.)
+
+If devices are configured different, the cluster will not start.
+If no header is on the devices, the cluster starts and keeps looking for a
+valid header.
+
+.B ** Three devices
+
+In this most reliable configuration, SBD will only commit suicide if more
+than one device is lost; hence, this configuration is resilient against
+one device outages (be it due to failures or maintenance). Fencing
+messages can be successfully relayed if at least two devices remain up.
+
+If one device out of three is completely missing at cluster start, the cluster
+will start. If one device out of three is available, but mis-configured, the
+cluster will not start. If two devices are completely missing, the cluster
+will also not start.
+
+This configuration is appropriate for more complex scenarios where storage
+is not confined to a single array.
+
+Host-based mirroring solutions could have one SBD per mirror leg (not
+mirrored itself), and an additional tie-breaker on iSCSI.
+
+.\"
+.P
+\fB* Pre-Requisites\fR
+
+The environment must have shared storage reachable by all nodes.
+You must dedicate a small partition of each as the SBD device.
+This shared storage segment must not make use of host-based RAID, cLVM2,
+nor DRBD.
+
+The SBD device can be connected via Fibre Channel, Fibre Channel over
+Eterhnet, or even iSCSI. Thus, an iSCSI target can become a sort-of
+network-based quorum server; the advantage is that it does not require
+a smart host at your third location, just block storage.
+
+However, using storage-based RAID and multipathing is recommended for
+increased reliability.
+.\"
+.P
+\fB* SBD Partition\fR
+
+It is recommended to create a tiny partition at the start of the device.
+In the rest of this text, this is referred to as "/dev/<SBD>" or "/dev/<SBD_n>",
+please substitute your actual pathnames
+(f.e. "/dev/disk/by-id/scsi-1494554000000000036363600000000000000000000000000-part1")
+for this below.
+
+The size of the SBD device depends on the block size of the underlying
+device. SBD uses 255 slots. Thus, 1MB is fine on plain SCSI devices and
+SAN storages with 512 byte blocks. On the IBM s390x architecture disks could
+have larger block sizes, as 4096 bytes. Therefor 4MB or more are needed there.
+
+After having made very sure that this is indeed the device you want to
+use, and does not hold any data you need - as the sbd command will
+overwrite it without further requests for confirmation -, initialize the
+sbd device.
+
+If your SBD device resides on a multipath group, you may need to adjust
+the timeouts sbd uses, as MPIO's path down detection can cause some
+latency: after the msgwait timeout, the message is assumed to have been
+delivered to the node. For multipath, this should be the time required
+for MPIO to detect a path failure and switch to the next path. You may
+have to test this in your environment. The node will perform suicide if
+it has not updated the watchdog timer fast enough; the watchdog timeout
+must be shorter than the msgwait timeout - half the value is a good
+estimate. This can be specified when the SBD device is initialized.
+.\"
+.P
+\fB* Testing and Starting the SBD Daemon\fR
+
+The sbd daemon is a critical piece of the cluster stack. It must always
+be running when the cluster stack is up, or even when the rest of it has
+crashed, so that it can be fenced.
+
+The openais init script starts and stops SBD if configured; add the
+following to /etc/sysconfig/sbd:
+
+===
+.br
+#/etc/sysconfig/sbd
+.br
+# SBD devices (no trailing ";"):
+.br
+SBD_DEVICE="/dev/<SBD_1>;/dev/<SBD_2>;/dev/<SBD_3>"
+.br
+# Watchdog support:
+.br
+SBD_OPTS="-W -t300"
+.br
+===
+
+Note: If the SBD device becomes inaccessible from a node, this could
+cause the node to enter an infinite reboot cycle. That is technically
+correct, but depending on your administrative policies, might be
+considered a nuisance. You may wish to not automatically start up
+openais on boot in such cases.
+
+Before proceeding, ensure that SBD has indeed started on all nodes
+through "rcopenais restart".
+Once the resource has started, your cluster is now successfully
+configured for shared-storage fencing, and will utilize this method in
+case a node needs to be fenced.
+
+The command sbd
+can be used to read and write the sbd device, see sbd(8) .
+
+To complete the sbd setup, it is necessary to activate SBD as a
+STONITH/fencing mechanism in the CIB.
+The SBD mechanism is used instead of other fencing/stonith mechanisms;
+please disable any others you might have configured before.
+.\"
+.P
+\fB* Software Watchdog\fR
+
+Increased protection is offered through "watchdog" support. Modern
+systems support a "hardware watchdog" that has to be updated by the
+software client, or else the hardware will enforce a system restart.
+This protects against failures of the sbd process itself, such as
+dieing, or becoming stuck on an IO error.
+
+It is highly recommended that you set up your Linux system
+to use a watchdog. Please refer to the SLES manual for this step.
+
+This involves loading the proper watchdog driver on system boot. On HP
+hardware, this is the "hpwdt" module. For systems with a Intel TCO,
+"iTCO_wdt" can be used. "softdog" is the most generic driver, but it is
+recommended that you use one with actual hardware integration. See
+/lib/modules/.../kernel/drivers/watchdog in the kernel package for a list
+of choices.
+
+No other software must access the watchdog timer. Some hardware vendors
+ship systems management software that use the watchdog for system resets
+(f.e. HP ASR daemon). Such software has to be disabled if the watchdog is
+used by SBD.
+
+SBD can be configured in /etc/sysconfig/sbd to use the systems' watchdog.
+.\"
+.P
+\fB* Timeout Settings\fR
+
+If your SBD device resides on a multipath group, you may need to adjust
+the timeouts sbd uses, as MPIO's path down detection can cause some
+latency: after the msgwait timeout, the message is assumed to have been
+delivered to the node. For multipath, this should be the time required
+for MPIO to detect a path failure and switch to the next path. You may
+have to test this in your environment. The node will perform suicide if
+it has not updated the watchdog timer fast enough; the watchdog timeout
+must be shorter than the msgwait timeout - half the value is a good
+estimate. This can be specified when the SBD device is initialized.
+
+If you want to avoid MD mirror splitting in case of IO errors, the watchdog
+timeout has to be shorter than the total MPIO failure timeout. Thus, a node
+is fenced before the MD mirror is splitted. On the other hand, the time
+the cluster waits for SAN and storage to recover is shortened.
+
+In any case, the watchdog timeout must be shorter than sbd message wait timeout.
+The sbd message wait timeout must be shorter than the cluster stonith-timeout.
+
+If the sbd device recovers from IO errors within the watchdog timeout, the sbd
+daemon could reset the watchdog timer and save the node from being fenced.
+To allow re-discovery of a failed sbd device, at least the primary sbd retry
+cycle should be shorter than the watchdog timeout. Since this cycle is currently
+hardcoded as ten time the loop timeout, it has to be set by choosing an
+apropriate loop timeout.
+
+It might be also wise to set a start delay for the cluster resource agent in
+the CIB. This is done to overcome situations where both nodes fence each other
+within the sbd loop timeout, see sbd(8).
+
+Putting it all together:
+.br
+- How long a cluster survives a storage outage depends on the watchdog
+ timeout and the sbd retry cycle. All other timeouts should be aligned with
+ this settings. That means they have to be longer.
+.br
+- Storage resources - as Raid1, LVM, Filesystem - have operation timeouts.
+ Those should be aligned with the MPIO settings. This avoids non-needed failure
+ actions, but does not define how long the cluster will survive a storage
+ outage.
+.\"
+.SH FILES
+.TP
+/usr/sbin/sbd
+ the daemon (and control command).
+.TP
+/usr/lib64/stonith/plugins/external/sbd
+ the STONITH plugin.
+.TP
+/etc/sysconfig/sbd
+ the SBD configuration file.
+.TP
+/etc/sysconfig/kernel
+ the kernel and initrd configuration file.
+.TP
+/etc/rc.d/rc3.d/K01openais
+ stop script to prevent stonith during system shutdown.
+.TP
+/dev/<SBD>
+ the SBD block device(s).
+.TP
+/dev/watchdog
+ the watchdog device node.
+.TP
+/lib/modules/<kernel-version>/kernel/drivers/watchdog/
+ the watchdog modules.
+.\"
+.SH BUGS
+To report bugs for a SUSE or Novell product component, please use
+ http://support.novell.com/additional/bugreport.html .
+.\"
+.SH SEE ALSO
+
+\fBsbd\fP(8), \fBadd_watchdog_to_initrd\fP(8), \fBdisable_other_watchdog\fP(8),
+\fBmake_sbd_devices\fP(8), \fBdasdfmt\fP(8),
+http://www.linux-ha.org/wiki/SBD_Fencing ,
+http://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg03849.html ,
+http://www.novell.com/documentation/sle_ha/book_sleha/?page=/documentation/sle_ha/book_sleha/data/part_config.html ,
+http://www.novell.com/documentation/sle_ha/book_sleha/?page=/documentation/sle_ha/book_sleha/data/part_storage.html
+.\"
+.SH AUTHORS
+The content of this manual page was mostly derived from online documentation
+mentioned above.
+.\"
+.SH COPYRIGHT
+(c) 2009-2011 SUSE Linux GmbH, Germany.
+.br
+sbd comes with ABSOLUTELY NO WARRANTY.
+.br
+For details see the GNU General Public License at
+http://www.gnu.org/licenses/gpl.html
+.\"
diff --git a/man/sbd.8 b/man/sbd.8
new file mode 100644
index 0000000..dc57bce
--- /dev/null
+++ b/man/sbd.8
@@ -0,0 +1,338 @@
+.TH sbd 8 "16 Jan 2012" "" "cluster-glue"
+.\"
+.SH NAME
+sbd \- Stonith Block Device daemon
+.\"
+.SH SYNOPSIS
+.B sbd
+\fIOPTIONS\fR [\fIOPT_ARGUMENT\fR] [\fICOMMAND\fR] [\fICMD_ARGUMENT\fR]
+
+.\"
+.SH OPTIONS
+.TP
+\fB-d\fR <SBD>
+ Block device to use (mandatory),
+if you have more than one device, provide them by specifying this
+option multiple times
+.TP
+\fB-h\fR
+ Display this help
+.TP
+\fB-n\fR <node>
+ Set local node name; defaults to uname -n (optional)
+.TP
+\fB-R\fR
+ Do NOT enable realtime priority (debugging only)
+.TP
+\fB-W\fR
+ Use watchdog (recommended) (watch only)
+.TP
+\fB-w\fR <SBD>
+ Specify watchdog device (optional) (watch only)
+.TP
+\fB-D\fR
+ Run as background daemon (optional) (watch only)
+.TP
+\fB-t\fR <N>
+ Set timeout to <N> seconds before automatic recover of failed SBD device
+(optional) (default is 3600, set to 0 to disable) (watch only)
+.TP
+\fB-v\fR
+ Enable some verbose debug logging (optional)
+.TP
+\fB-1\fR <N>
+ Set watchdog timeout to N seconds (optional) (create only)
+.TP
+\fB-2\fR <N>
+ Set slot allocation timeout to N seconds (optional) (create only)
+.TP
+\fB-3\fR <N>
+ Set daemon loop timeout to N seconds (optional) (create only)
+.TP
+\fB-4\fR <N>
+ Set msgwait timeout to N seconds (optional) (create only)
+.TP
+\fB-5\fR <N>
+ Warn if loop latency exceeds threshold (optional) (watch only)
+(default is 3, set to 0 to disable)
+
+.\"
+.SH COMMAND
+.TP
+\fBcreate\fR
+ Initialize N slots on devicde <SBD> - OVERWRITES DEVICE!
+.TP
+\fBlist\fR
+ List all allocated slots on device, and messages.
+.TP
+\fBdump\fR
+ Dump meta-data header from device.
+.TP
+\fBwatch\fR
+ Loop forever, monitoring own slot
+.TP
+\fBallocate\fR <node>
+ Allocate a slot for node (optional)
+.TP
+\fBmessage\fR <node> (test|reset|off|clear|exit)
+ Write the specified message to node's slot.
+
+.\"
+.SH DESCRIPTION
+
+The \fBsbd\fR daemon automatically allocates one of the message slots on the
+assigned disk partition to itself, and constantly monitors it for messages to
+itself. Upon receipt of a message, the daemon immediately complies with the
+request, such as initiating a power-off or reboot cycle for fencing.
+
+The daemon also constantly monitors connectivity to the storage device,
+and commits suicide in case the partition becomes unreachable,
+guaranteeing that it is not disconnected from fencing message.
+
+The daemon is brought online on each node before the rest of the
+cluster stack is started, and terminated only after all other cluster
+components have been shut down - ensuring that cluster resources are
+never activated without SBD supervision.
+
+The environment must have shared storage reachable by all nodes.
+This shared storage segment must not make use of host-based RAID, cLVM2,
+nor DRBD. Please refer to sbd(7) for more information.
+
+The \fBsbd\fR can also be called manually to perform actions described in the
+commands section of this manual page.
+
+In the rest of this text, this is referred to as "/dev/<SBD>" or "/dev/<SBD_n>",
+please substitute your actual pathname
+(f.e. "/dev/disk/by-id/scsi-1494554000000000036363600000000000000000000000000")
+for this below.
+
+If a watchdog is used together with the sbd, the watchdog is activated at initial
+start of the sbd daemon. Afterwards the watchdog timer is reset by the inquisitor
+process after each successful read loop of each watcher process.
+
+STONITH is an acronym for Shoot The Other Node in The Head.
+.\"
+.SH EXAMPLES
+
+
+\fB* Initialising SBD Partition\fR
+
+All these steps must be performed as root.
+
+After having made very sure that this is indeed the device you want to
+use, and does not hold any data you need - as the sbd command will
+overwrite it without further requests for confirmation -, initialize one
+single SBD device:
+
+# \fBsbd -d /dev/<SBD> create\fR
+
+This will write a header to the device, and create slots for up to 255
+nodes sharing this device with default timings.
+
+If your sbd device resides on a multipath group, you may need to adjust
+the timeouts sbd uses, as MPIO's path down detection can cause some
+latency: after the msgwait timeout, the message is assumed to have been
+delivered to the node. For multipath, this should be the time required
+for MPIO to detect a path failure and switch to the next path. You may
+have to test this in your environment.
+
+Initialize three SBD devices in exact the same way, with identical settings:
+
+# \fBsbd -d /dev/<SBD_1> -d /dev/<SBD_2> -d /dev/<SBD_3> create\fR
+
+
+\fB* Setting Watchdog Timeout for SBD Partition\fR
+
+The node will perform suicide if
+it has not updated the watchdog timer fast enough; the watchdog timeout
+must be shorter than the msgwait timeout - half the value is a good
+estimate. This can be specified when the SBD device is initialized:
+
+# \fB/usr/sbin/sbd -d /dev/<SBD> -4 $msgwait -3 $looptimeout -1 $watchdogtimeout create\fR
+
+(All timeouts are in seconds. See also sbd(7) for information on timings.)
+
+If your single sbd device resides on a multipath group, you may need to
+adjust the timeouts sbd uses, as MPIO's path down detection can cause
+delays. (If you have multiple devices, transient timeouts of a single
+device will not negatively affect SBD. However, if they all go through
+the same FC switches, you will still need to do this.)
+
+
+\fB* Dumping Content of SBD Partition\fR
+
+You can look at what was written to the device using:
+
+# \fBsbd -d /dev/<SBD> dump\fR
+.br
+Header version : 2
+.br
+Number of slots : 255
+.br
+Sector size : 512
+.br
+Timeout (watchdog) : 5
+.br
+Timeout (allocate) : 2
+.br
+Timeout (loop) : 1
+.br
+Timeout (msgwait) : 10
+
+As you can see, the timeouts are also stored in the header, to ensure
+that all participating nodes agree on them. The example output above
+shows built-in defaults. Usually the timeouts for watchdog and msgwait
+are adjusted to specific needs, see sbd(7). The timeouts for allocate
+and loop normally should not be changed.
+
+Additionally, it is highly recommended that you set up your Linux system
+to use a watchdog.
+
+
+\fB* Starting the SBD daemon\fR
+
+The sbd daemon is a critical piece of the cluster stack. It must always
+be running when the cluster stack is up, or even when the rest of it has
+crashed, so that it can be fenced.
+
+The openais init script starts and stops SBD if configured; add the
+following to /etc/sysconfig/sbd:
+
+===
+.br
+# The next line points to three devices (no trailing ";"):
+.br
+SBD_DEVICE="/dev/<SBD_1>;/dev/<SBD_2>;/dev/<SBD_3>"
+.br
+# The next line enables watchdog support, re-discover time 210 seconds:
+.br
+SBD_OPTS="-W -t 210"
+.br
+===
+
+Before proceeding, ensure that SBD has indeed started on all nodes through
+
+# \fBrcopenais restart\fR
+
+
+\fB* Listing Content of SBD\fR
+
+The command
+
+# \fBsbd -d /dev/<SBD> list\fR
+
+will dump the node slots, and their current messages, from the sbd
+device. You should see all cluster nodes that have ever been started
+with sbd being listed there; most likely with the message slot showing
+"clear".
+
+
+\fB* Testing SBD\fR
+
+You can now try sending a test message to one of the nodes:
+
+# \fBsbd -d /dev/<SBD> message nodea test\fR
+
+The node will acknowledge the receipt of the message in the system logs:
+.br
+Aug 29 14:10:00 nodea sbd: [13412]: info: Received command test from nodeb
+
+This confirms that SBD is indeed up and running on the node, and that it
+is ready to receive messages.
+
+
+\fB* Recovering from temporary SBD device outage\fR
+
+If you have multiple devices, failure of a single device is not immediately
+fatal.
+SBD will retry ten times in succession to reattach to the device, and then pause
+(as to not flood the system) before retrying. The pause intervall timeout could
+ be configured. Thus, SBD should automatically recover from temporary outages.
+
+Should you wish to try reattach to the device right now, you can send a SIGUSR1
+to the SBD parent daemon.
+
+# \fBps aux | grep sbd\fR
+.br
+root 3363 0.0 1.0 44552 5764 ? SL Dec16 0:13 sbd: inquisitor
+.br
+root 3364 0.0 1.0 44568 5712 ? SL Dec16 0:32 sbd: watcher: /dev/disk/by-id/scsi-1494554000000000036363600000000000000000000000000-part1 - slot: 0
+.br
+# \fBkill -SIGUSR1 3363\fR
+.br
+# \fBps aux | grep sbd\fR
+.br
+root 3363 0.0 1.0 44552 5764 ? SL Dec16 0:13 sbd: inquisitor
+.br
+root 3364 0.0 1.0 44568 5712 ? SL Dec16 0:32 sbd: watcher: /dev/disk/by-id/scsi-1494554000000000036363600000000000000000000000000-part1 - slot: 0
+.br
+root 3380 0.0 1.0 44568 5712 ? SL Dec16 0:00 sbd: watcher: /dev/disk/by-id/scsi-1494554000000000038383800000000000000000000000000-part1 - slot: 0
+.\" check the fake
+
+There are two to four sbd processes, depending on the number of sbd devices:
+One master process (inquisitor), and per device one watcher.
+
+\fB* Configuring the Fencing Resource in the Cluster Information Base\fR
+
+To complete the sbd setup, it is necessary to activate sbd as a
+STONITH/fencing mechanism in the CIB as follows:
+
+# \fBcrm
+.br
+configure
+.br
+property stonith-enabled="true"
+.br
+property stonith-timeout="150s"
+.br
+primitive stonith_sbd stonith:external/sbd
+op start interval="0" timeout="15" start-delay="5"
+.br
+commit
+.br
+quit
+\fR
+
+Note that since node slots are allocated automatically, no manual hostlist needs
+to be defined. Also, there is no need to define the SBD devices. On the other hand,
+ a start delay is set. This is done to overcome situations where both nodes fence
+each other within the sbd loop timeout.
+
+Once the resource has started, your cluster is now successfully
+configured for shared-storage fencing, and will utilize this method in
+case a node needs to be fenced.
+
+The sbd agent does not need to and should not be cloned. If all of your nodes
+run SBD, as is most likely, not even a monitor action provides a real benefit,
+since the daemon would suicide the node if there was a problem.
+
+SBD also supports turning the reset request into a crash request, which may be
+helpful for debugging if you have kernel crashdumping configured; then, every
+fence request will cause the node to dump core. You can enable this via the
+crashdump="true" setting on the fencing resource. This is not recommended for
+on-going production use, but for debugging phases.
+.\"
+.SH BUGS
+To report bugs for a SUSE or Novell product component, please use
+ http://support.novell.com/additional/bugreport.html .
+.\"
+.SH SEE ALSO
+
+\fBsbd\fP(7),
+http://www.linux-ha.org/wiki/SBD_Fencing ,
+http://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg03849.html ,
+http://www.novell.com/documentation/sle_ha/book_sleha/?page=/documentation/sle_ha/book_sleha/data/part_config.html ,
+http://www.novell.com/documentation/sle_ha/book_sleha/?page=/documentation/sle_ha/book_sleha/data/part_storage.html
+.\"
+.SH AUTHORS
+The content of this manual page was mostly derived from online documentation
+mentioned above and the programm's help option.
+.\"
+.SH COPYRIGHT
+(c) 2009-2011 SUSE Linux GmbH, Germany.
+.br
+sbd comes with ABSOLUTELY NO WARRANTY.
+.br
+For details see the GNU General Public License at
+http://www.gnu.org/licenses/gpl.html
+.\"

File Metadata

Mime Type
text/x-diff
Expires
Wed, Feb 26, 5:13 PM (39 m, 1 s ago)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
1465589
Default Alt Text
(26 KB)

Event Timeline