/usr/share/doc/drbd-doc/users-guide/s-ocfs2-legacy.html is in drbd-doc 8.4~20140825-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 | <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.5. Legacy OCFS2 management (without Pacemaker)</title><link rel="stylesheet" type="text/css" href="default.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /><link rel="home" href="drbd-users-guide.html" title="The DRBD User’s Guide" /><link rel="up" href="ch-ocfs2.html" title="Chapter 12. Using OCFS2 with DRBD" /><link rel="prev" href="s-ocfs2-pacemaker.html" title="12.4. Pacemaker OCFS2 management" /><link rel="next" href="ch-xen.html" title="Chapter 13. Using Xen with DRBD" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">12.5. Legacy OCFS2 management (without Pacemaker)</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="s-ocfs2-pacemaker.html">Prev</a> </td><th width="60%" align="center">Chapter 12. Using OCFS2 with DRBD</th><td width="20%" align="right"> <a accesskey="n" href="ch-xen.html">Next</a></td></tr></table><hr /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="s-ocfs2-legacy"></a>12.5. Legacy OCFS2 management (without Pacemaker)</h2></div></div></div><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="images/important.png" /></td><th align="left">Important</th></tr><tr><td align="left" valign="top"><p>The information presented in this section applies to legacy
systems where OCFS2 DLM support is not available in Pacemaker. It is
preserved here for reference purposes only. New installations should
always use the <a class="link" href="s-ocfs2-pacemaker.html" title="12.4. Pacemaker OCFS2 management">Pacemaker</a> approach.</p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="s-ocfs2-enable"></a>12.5.1. Configuring your cluster to support OCFS2</h3></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="s-ocfs2-create-cluster-conf"></a>Creating the configuration file</h4></div></div></div><p>OCFS2 uses a central configuration file, <code class="literal">/etc/ocfs2/cluster.conf</code>.</p><p>When creating your OCFS2 cluster, be sure to add both your hosts to
the cluster configuration. The default port (7777) is usually an
acceptable choice for cluster interconnect communications. If you
choose any other port number, be sure to choose one that does not
clash with an existing port used by DRBD (or any other configured
TCP/IP).</p><p>If you feel less than comfortable editing the <code class="literal">cluster.conf</code> file
directly, you may also use the <code class="literal">ocfs2console</code> graphical configuration
utility which is usually more convenient. Regardless of the approach
you selected, your <code class="literal">/etc/ocfs2/cluster.conf</code> file contents should look
roughly like this:</p><pre class="programlisting">node:
ip_port = 7777
ip_address = 10.1.1.31
number = 0
name = alice
cluster = ocfs2
node:
ip_port = 7777
ip_address = 10.1.1.32
number = 1
name = bob
cluster = ocfs2
cluster:
node_count = 2
name = ocfs2</pre><p>When you have configured you cluster configuration, use <code class="literal">scp</code> to
distribute the configuration to both nodes in the cluster.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="s-configure-o2cb-driver"></a>Configuring the O2CB driver</h4></div></div></div><p>====== SUSE Linux Enterprise systems</p><p>On SLES, you may utilize the <code class="literal">configure</code> option of the <code class="literal">o2cb</code> init
script:</p><pre class="screen">/etc/init.d/o2cb configure
Configuring the O2CB driver.
This will configure the on-boot properties of the O2CB driver.
The following questions will determine whether the driver is loaded on
boot. The current values will be shown in brackets ('[]'). Hitting
<ENTER> without typing an answer will keep that current value. Ctrl-C
will abort.
Load O2CB driver on boot (y/n) [y]:
Cluster to start on boot (Enter "none" to clear) [ocfs2]:
Specify heartbeat dead threshold (>=7) [31]:
Specify network idle timeout in ms (>=5000) [30000]:
Specify network keepalive delay in ms (>=1000) [2000]:
Specify network reconnect delay in ms (>=2000) [2000]:
Use user-space driven heartbeat? (y/n) [n]:
Writing O2CB configuration: OK
Loading module "configfs": OK
Mounting configfs filesystem at /sys/kernel/config: OK
Loading module "ocfs2_nodemanager": OK
Loading module "ocfs2_dlm": OK
Loading module "ocfs2_dlmfs": OK
Mounting ocfs2_dlmfs filesystem at /dlm: OK
Starting O2CB cluster ocfs2: OK</pre><p>====== .Debian GNU/Linux systems
On Debian, the <code class="literal">configure</code> option to <code class="literal">/etc/init.d/o2cb</code> is not
available. Instead, reconfigure the <code class="literal">ocfs2-tools</code> package to enable the
driver:</p><pre class="screen">dpkg-reconfigure -p medium -f readline ocfs2-tools
Configuring ocfs2-tools
Would you like to start an OCFS2 cluster (O2CB) at boot time? yes
Name of the cluster to start at boot time: ocfs2
The O2CB heartbeat threshold sets up the maximum time in seconds that a node
awaits for an I/O operation. After it, the node "fences" itself, and you will
probably see a crash.
It is calculated as the result of: (threshold - 1) x 2.
Its default value is 31 (60 seconds).
Raise it if you have slow disks and/or crashes with kernel messages like:
o2hb_write_timeout: 164 ERROR: heartbeat write timeout to device XXXX after NNNN
milliseconds
O2CB Heartbeat threshold: `31`
Loading filesystem "configfs": OK
Mounting configfs filesystem at /sys/kernel/config: OK
Loading stack plugin "o2cb": OK
Loading filesystem "ocfs2_dlmfs": OK
Mounting ocfs2_dlmfs filesystem at /dlm: OK
Setting cluster stack "o2cb": OK
Starting O2CB cluster ocfs2: OK</pre></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="s-ocfs2-use"></a>12.5.2. Using your OCFS2 filesystem</h3></div></div></div><p>When you have completed cluster configuration and created your file
system, you may mount it as any other file system:</p><pre class="screen">mount -t ocfs2 /dev/drbd0 /shared</pre><p>Your kernel log (accessible by issuing the command <code class="literal">dmesg</code>) should
then contain a line similar to this one:</p><pre class="programlisting">ocfs2: Mounting device (147,0) on (node 0, slot 0) with ordered data mode.</pre><p>From that point forward, you should be able to simultaneously mount
your OCFS2 filesystem on both your nodes, in read/write mode.</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="s-ocfs2-pacemaker.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch-ocfs2.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch-xen.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">12.4. Pacemaker OCFS2 management </td><td width="20%" align="center"><a accesskey="h" href="drbd-users-guide.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 13. Using Xen with DRBD</td></tr></table></div></body></html>
|