[DRBD-cvs] svn commit by phil - r2870 - trunk/documentation - A
number spelling fixes in the documentation.
drbd-cvs at lists.linbit.com
drbd-cvs at lists.linbit.com
Sun May 6 22:02:09 CEST 2007
Author: phil
Date: 2007-05-06 22:02:07 +0200 (Sun, 06 May 2007)
New Revision: 2870
Modified:
trunk/documentation/drbd.conf.sgml
trunk/documentation/drbdadm.sgml
trunk/documentation/drbddisk.sgml
trunk/documentation/drbdmeta.sgml
trunk/documentation/drbdsetup.sgml
Log:
A number spelling fixes in the documentation.
Modified: trunk/documentation/drbd.conf.sgml
===================================================================
--- trunk/documentation/drbd.conf.sgml 2007-05-04 20:56:17 UTC (rev 2869)
+++ trunk/documentation/drbd.conf.sgml 2007-05-06 20:02:07 UTC (rev 2870)
@@ -55,14 +55,14 @@
The device which runs
on host <replaceable>thost1</replaceable> uses
<replaceable>/dev/drbd1</replaceable> as devices for its application, and
- <replaceable>/dev/hda7</replaceable> as low level storage for the data.
- The IP addresses are used to specify the networking interfaces to use.
+ <replaceable>/dev/hda7</replaceable> as low-level storage for the data.
+ The IP addresses are used to specify the networking interfaces to be used.
An eventually running resyncprocess should use about 10MByte/second of IO
- bandwith.
+ bandwidth.
</para>
<para>
There may be multiple resource sections in a single drbd.conf file.
- For more examples please have a look at the
+ For more examples, please have a look at the
<ulink url="http://www.linux-ha.org/DRBD/QuickStart07">
<citetitle>DRBD Quickstart Guide</citetitle></ulink>.
</para>
@@ -83,7 +83,7 @@
A parameter starts with the identifier of the parameter followed
by whitespace. Every subsequent character
is considered
- as part of the parameters value. A special case are Boolean
+ as part of the parameter's value. A special case are Boolean
parameters which only consist of the identifier.
Parameters are terminated by a semicolon (<quote>;</quote>).
</para>
@@ -105,7 +105,7 @@
<indexterm><primary>drbd.conf</primary><secondary>skip</secondary></indexterm>
Comments out chunks of text, even spanning more than one line.
Characters between the keyword <option>skip</option> and the opening
- brace (<quote>{</quote>)are ignored. Everything enclosed by the braces
+ brace (<quote>{</quote>) are ignored. Everything enclosed by the braces
is skipped.
This comes in handy, if you just want to comment out
some 'resource [name] {...}' section: just precede it with 'skip'.
@@ -131,7 +131,7 @@
<listitem><para>
<indexterm><primary>drbd.conf</primary><secondary>common</secondary></indexterm>
All resources interhit the options set in this section.
- The common section might have a
+ The common section might have
a <option>startup</option>,
a <option>syncer</option>,
a <option>handlers</option>,
@@ -193,7 +193,7 @@
<indexterm><primary>drbd.conf</primary><secondary>net</secondary></indexterm>
This section is used to fine tune DRBD's properties. Please
refer to <citerefentry><refentrytitle>drbdsetup</refentrytitle>
- <manvolnum>8</manvolnum></citerefentry> for detailed description
+ <manvolnum>8</manvolnum></citerefentry> for a detailed description
of this section's parameters.
Optional parameters:
<option>sndbuf-size</option>, <option>timeout</option>,
@@ -214,7 +214,7 @@
<indexterm><primary>drbd.conf</primary><secondary>startup</secondary></indexterm>
This section is used to fine tune DRBD's properties. Please
refer to <citerefentry><refentrytitle>drbdsetup</refentrytitle>
- <manvolnum>8</manvolnum></citerefentry> for detailed description
+ <manvolnum>8</manvolnum></citerefentry> for a detailed description
of this section's parameters.
Optional parameters:
<option>wfc-timeout</option>, <option>degr-wfc-timeout</option>.
@@ -229,7 +229,7 @@
This section is used to fine tune the synchronisation daemon
for the device. Please
refer to <citerefentry><refentrytitle>drbdsetup</refentrytitle>
- <manvolnum>8</manvolnum></citerefentry> for detailed description
+ <manvolnum>8</manvolnum></citerefentry> for a detailed description
of this section's parameters.
Optional parameters:
<option>rate</option>, <option>after</option>, <option>al-extents</option>.
@@ -241,7 +241,7 @@
<term><option>handlers</option></term>
<listitem><para>
<indexterm><primary>drbd.conf</primary><secondary>handlers</secondary></indexterm>
- In this section can define handlers (executables) that are executed
+ In this section you can define handlers (executables) that are executed
by the DRBD system in response to certain events.
Optional parameters:
<option>pri-on-incon-degr</option>, <option>pri-lost-after-sb</option>,
@@ -268,7 +268,7 @@
<para>Use <replaceable>minor-count</replaceable>
if you want to define massively more resources later without reloading
the DRBD kernel
- module. Per default the module loads with 11 more than you have currently
+ module. Per default the module loads with 11 more resources than you have currently
in your config but at least 32.</para>
</listitem>
</varlistentry>
@@ -279,9 +279,9 @@
<indexterm><primary>drbd.conf</primary><secondary>dialog-refresh </secondary></indexterm>
<replaceable>time</replaceable> may be 0 or a positive number.
</para>
- <para>The user dialog redraws the second count every
+ <para>The user dialogue redraws the second count every
<replaceable>time</replaceable> seconds (or does no redraws if
- <replaceable>time</replaceable> is zero). The default is 1.</para>
+ <replaceable>time</replaceable> is 0). The default value is 1.</para>
</listitem>
</varlistentry>
@@ -291,7 +291,7 @@
<indexterm><primary>drbd.conf</primary><secondary>disable-ip-verification</secondary></indexterm>
<para>Use <replaceable>disable-ip-verification</replaceable>
if, for some obscure reasons, drbdadm can/might not use ip or ifconfig
- to do a sanity check for the IP address, you can disable it with this
+ to do a sanity check for the IP address. You can disable the IP verification with
this option.
</para>
</listitem>
@@ -331,7 +331,7 @@
<listitem><para>
<indexterm><primary>drbd.conf</primary><secondary>incon-degr-cmd</secondary></indexterm>
In case a node starts up in degraded mode (degr-wfc-timeout is set) and
- its local replica of the data is inconsistent it executes the
+ its local replica of the data is inconsistent, it executes the
<replaceable>command</replaceable>. If the command exits without
error, drbddisk expects the DRBD device to be in primary state.
</para>
@@ -349,13 +349,13 @@
</para>
<para>
The device nodes must have the same major number as the DRBD
- driver has. With the current implementation major 147 is used
+ driver. With the current implementation major 147 is used
and the corresponding device nodes are usually named
<option>/dev/drbd0</option>, <option>/dev/drbd1</option>, etc.
( All releases before drbd-0.7.1 used major 43 and the device
files /dev/nb*. )
</para>
- <para>Installation scripts of the DRBD package provide, that
+ <para>Installation scripts of the DRBD package require that
<option>/dev/drbd0</option> to <option>/dev/drbd8</option> are
predefined in your system. To be sure, issue something like ls /dev/drbd*.
</para>
@@ -400,9 +400,9 @@
<listitem><para>
<indexterm><primary>drbd.conf</primary><secondary>meta-disk</secondary></indexterm>
<indexterm><primary>drbd.conf</primary><secondary>flexible-meta-disk</secondary></indexterm>
- internal means, that the last part of the backing device are used to store
+ Internal means that the last part of the backing device is used to store
the meta-data. You must not use <replaceable>[index]</replaceable> with
- internal. Note: Regardless if you use the <option>meta-disk</option> or
+ internal. Note: Regardless of whether you use the <option>meta-disk</option> or
the <option>flexible-meta-disk</option> keyword, it will always be of
the size needed for the remaining storage size.
</para>
@@ -439,10 +439,9 @@
</para>
<para>pass_on: Report the io-error to the upper layers. On Primary report
it to the mounted file system. On Secondary ignore it.</para>
- <para>call-local-io-error: Thall the handler script
+ <para>call-local-io-error: Call the handler script
<option>local-io-error</option>.</para>
- <para>detach: The node drops its low level device, and continues in disk
- less mode.</para>
+ <para>detach: The node drops its low level device, and continues in diskless mode.</para>
</listitem>
</varlistentry>
@@ -450,7 +449,7 @@
<term><option>fencing <replaceable>fencing_policy</replaceable></option></term>
<listitem><para>
<indexterm><primary>drbd.conf</primary><secondary>fencing</secondary></indexterm>
- Under <option>fencing</option> we understand preventative
+ Under <option>fencing</option> we understand preventive
measures to avoid situations where both nodes are primary
and disconnected (AKA split brain).
</para>
@@ -462,21 +461,21 @@
</para></listitem></varlistentry>
<varlistentry><term><option>resource-only</option></term>
<listitem><para>
- If a node becomes a disconnected primary it tries to outdate
+ If a node becomes a disconnected primary, it tries to outdate
the peer's disk. This is done by calling the outdate-peer
handler. The handler is supposed to reach the other node over
- alternative communication pathes and call 'drbdadm outdate
+ alternative communication paths and call 'drbdadm outdate
res' there.
</para></listitem></varlistentry>
<varlistentry><term><option>resource-and-stonith</option></term>
<listitem><para>
- If a node becomes a disconnected primary it freezes all
+ If a node becomes a disconnected primary, it freezes all
its IO operations and calls its outdate-peer handler. The
- outdate-peer hander is supposed to reach the peer over
- alternative communicaton pathes and call 'drbdadm outdate
- res' there. In case it can not reach the peer it should
+ outdate-peer handler is supposed to reach the peer over
+ alternative communicaton paths and call 'drbdadm outdate
+ res' there. In case it cannot reach the peer it should
stonith the peer. IO is resumed as soon as the situation
- is resolved. In case your handler fails you can resume
+ is resolved. In case your handler fails, you can resume
IO with the <option>resume-io</option> command.
</para></listitem></varlistentry>
</variablelist>
@@ -488,17 +487,17 @@
<listitem>
<indexterm><primary>drbd.conf</primary><secondary>use-bmbv</secondary></indexterm>
<para>
- In case the backing storage's driver has a merge_bvec_fn() function
- (At time of writing the only known drivers which have such a function
+ In case the backing storage's driver has a merge_bvec_fn() function,
+ DRBD has to pretend that it can only process IO requests in
+ units not lager than 4kByte. (At time of writing the only known drivers which have such a function
are: md (software raid driver), dm (device mapper - LVM) and DRBD
- itself) drbd has to pretend that it can only process IO requests in
- units not lager than 4kByte.</para>
+ itself)</para>
<para>
To get best performance out of DRBD on top of software raid (or any
other driver with a merge_bvec_fn() function) you might enable this
- function, iff you know for sure that the merge_bvec_fn() function will
+ function, if you know for sure that the merge_bvec_fn() function will
deliver the same results on all nodes of your cluster. I.e. the
- physical disks of the software raid are of the exact same type. USE
+ physical disks of the software raid are of exactly the same type. USE
THIS OPTION ONLY IF YOU KNOW WHAT YOU ARE DOING.</para>
</listitem>
</varlistentry>
@@ -507,10 +506,10 @@
<term><option>sndbuf-size <replaceable>size</replaceable></option></term>
<listitem><para>
<indexterm><primary>drbd.conf</primary><secondary>sndbuf-size </secondary></indexterm>
- <replaceable>size</replaceable> is size of the TCP socket send buffer.
- Default is 128K. You can specify smaller or larger values. Larger values
+ <replaceable>size</replaceable> is the size of the TCP socket send buffer.
+ The default value is 128K. You can specify smaller or larger values. Larger values
are appropriate for reasonable write throughput with protocol A over high
- latency networks. Very large values like 1M may cause problems. Even values
+ latency networks. Very large values like 1M may cause problems. Also values
below 32K do not make much sense.
</para>
</listitem>
@@ -553,9 +552,9 @@
<term><option>ping-timeout <replaceable>time</replaceable></option></term>
<listitem><para>
<indexterm><primary>drbd.conf</primary><secondary>ping-timeout</secondary></indexterm>
- The time the peer has time to answer to a keep-alive packet, it. In case
+ The time the peer has time to answer to a keep-alive packet. In case
the peer's reply is not received within this time period, it is
- considered as dead. The default is 500ms, the default unit is 100ms.
+ considered as dead. The default value is 500ms, the default unit is 100ms.
</para></listitem>
</varlistentry>
@@ -563,12 +562,12 @@
<term><option>max-buffers <replaceable>number</replaceable></option></term>
<listitem><para>
<indexterm><primary>drbd.conf</primary><secondary>max-buffers </secondary></indexterm>
- Maximal number of requests to be allocated by DRBD. Unit is PAGE_SIZE,
+ Maximum number of requests to be allocated by DRBD. Unit is PAGE_SIZE,
which is 4 KB on most systems.
The minimum is hardcoded to 32 (=128 KB).
- For high performance installations it might help, if you
+ For high-performance installations it might help, if you
increase that number. These buffers are used to hold
- datablocks while they are written to disk.
+ data blocks while they are written to disk.
</para></listitem>
</varlistentry>
@@ -580,7 +579,7 @@
request for <replaceable>count</replaceable> times the
<replaceable>timeout</replaceable>, it is expelled from the
cluster. (I.e. the primary node goes into StandAlone mode.)
- The default is 0, which disables this feature.
+ The default value is 0, which disables this feature.
</para></listitem>
</varlistentry>
@@ -589,7 +588,7 @@
<listitem><para>
<indexterm><primary>drbd.conf</primary><secondary>max-epoch-size </secondary></indexterm>
The highest number of data blocks between two write barriers.
- If you set this smaller than 10 you might decrease your performance.
+ If you set this smaller than 10, you might decrease your performance.
</para></listitem>
</varlistentry>
@@ -597,10 +596,10 @@
<term><option>allow-two-primaries</option></term>
<listitem><para>
<indexterm><primary>drbd.conf</primary><secondary>allow-two-primaries</secondary></indexterm>
- With this option set you might make both nodes primary. You only should
- use this options if you use a shared storage file system on top of
+ With this option set you may assign primary role to both nodes. You only should
+ use this option if you use a shared storage file system on top of
DRBD. At the time of writing the only ones are: OCFS2 and GFS. If you
- use this option with any other filesystem you are goint to crash your
+ use this option with any other file system, you are going to crash your
nodes and to corrupt your data!
</para></listitem>
</varlistentry>
@@ -614,7 +613,7 @@
(secondary) node exceeds the unplug-watermark, we trigger
the request processing of our backing storage device.
Some storage controllers deliver better performance with small
- values, other deliver best performance when it is set to
+ values, others deliver best performance when the value is set to
the same value as max-buffers. Minimum 16, default 128, maximum
131072.
</para>
@@ -625,10 +624,10 @@
<term><option>cram-hmac-alg</option></term>
<listitem><para>
<indexterm><primary>drbd.conf</primary><secondary>cram-hmac-alg</secondary></indexterm>
- You need to specifying the HMAC algorithm to enable peer authentication
- at all. It is strongly enouraged to use peer authentication. The HMAC
- algorithm which will be used for the challenge response authentication
- of the peer. You might specify any digest algorithm that is named in
+ You need to specify the HMAC algorithm to enable peer authentication
+ at all. You are strongly enouraged to use peer authentication. The HMAC
+ algorithm will be used for the challenge response authentication
+ of the peer. You may specify any digest algorithm that is named in
/proc/crypto.
</para></listitem>
</varlistentry>
@@ -655,13 +654,12 @@
</para></listitem></varlistentry>
<varlistentry><term><option>discard-younger-primary</option></term>
<listitem><para>
- Auto sync from the node that was primary before the split
- brain situation happened.
+ Auto sync from the node that was primary before the split-brain situation happened.
</para></listitem></varlistentry>
<varlistentry><term><option>discard-older-primary</option></term>
<listitem><para>
Auto sync from the node that became primary as second during
- the split brain situation.
+ the split-brain situation.
</para></listitem></varlistentry>
<varlistentry><term><option>discard-zero-changes</option></term>
<listitem><para>
@@ -701,18 +699,18 @@
<varlistentry><term><option>consensus</option></term>
<listitem><para>
Discard the version of the secondary if the outcome
- if the <option>after-sb-0pri</option> algorithm would also
+ of the <option>after-sb-0pri</option> algorithm would also
destroy the current secondary's data. Otherwise disconnect.
</para></listitem></varlistentry>
<varlistentry><term><option>violently-as0p</option></term>
<listitem><para>
- Always take the decission of the <option>after-sb-0pri</option>
- algorithm. Even if that causes case an erratic change of
- the primarie's view of the data. This is only usefull if
- you use an 1node FS (i.e. not OCFS2 or GFS) with the
- allow-two-primaries flag, _AND_ you really know what you
+ Always take the decision of the <option>after-sb-0pri</option>
+ algorithm. Even if that causes an erratic change of
+ the primary's view of the data. This is only useful if
+ you use a 1node FS (i.e. not OCFS2 or GFS) with the
+ allow-two-primaries flag, _AND_ if you really know what you
are doing. This is DANGEROUS and MAY CRASH YOUR MACHINE
- if you have a FS mounted on the primary node.
+ if you have an FS mounted on the primary node.
</para></listitem></varlistentry>
<varlistentry><term><option>discard-secondary</option></term>
<listitem><para>
@@ -721,7 +719,7 @@
<varlistentry><term><option>call-pri-lost-after-sb</option></term>
<listitem><para>
Always honour the outcome of the <option>after-sb-0pri
- </option> algorithm. In case it decides the the current
+ </option> algorithm. In case it decides the current
secondary has the right data, it calls the "pri-lost-after-sb"
handler on the current primary.
</para></listitem></varlistentry>
@@ -743,19 +741,19 @@
</para></listitem></varlistentry>
<varlistentry><term><option>violently-as0p</option></term>
<listitem><para>
- Always take the decission of the <option>after-sb-0pri</option>
- algorithm. Even if that causes case an erratic change of
- the primarie's view of the data. This is only usefull if
- you use an 1node FS (i.e. not OCFS2 or GFS) with the
- allow-two-primaries flag, _AND_ you really know what you
+ Always take the decision of the <option>after-sb-0pri</option>
+ algorithm. Even if that causes an erratic change of
+ the primary's view of the data. This is only useful if
+ you use a 1node FS (i.e. not OCFS2 or GFS) with the
+ allow-two-primaries flag, _AND_ if you really know what you
are doing. This is DANGEROUS and MAY CRASH YOUR MACHINE
- if you have a FS mounted on the primary node.
+ if you have an FS mounted on the primary node.
</para></listitem></varlistentry>
<varlistentry><term><option>call-pri-lost-after-sb</option></term>
<listitem><para>
Call the "pri-lost-after-sb" helper program on one of the
machines. This program is expected to reboot the
- machine. (I.e. make it secondary.)
+ machine, i.e. make it secondary.
</para></listitem></varlistentry>
</variablelist>
</listitem>
@@ -766,14 +764,14 @@
<listitem>
<para>
Normally the automatic after-split-brain policies are only
- used if current state of the UUIDs do not indicate the
+ used if current states of the UUIDs do not indicate the
presence of a third node.
</para>
<para>
With this option you request that the automatic
after-split-brain policies are used as long as the data
sets of the nodes are somehow related. This might cause
- a full sync, if the UUIDs indicates the presence of a third
+ a full sync, if the UUIDs indicate the presence of a third
node. (Or double faults led to strange UUID sets.)
</para>
</listitem>
@@ -784,8 +782,8 @@
<listitem>
<indexterm><primary>drbd.conf</primary><secondary>rr-conflict </secondary></indexterm>
<para>
- To solve the cases when the outcome of the resync decission is
- incompatible to the current role assignment in the cluster.
+ To solve the cases when the outcome of the resync decision is
+ incompatible with the current role assignment in the cluster.
</para>
<variablelist>
<varlistentry><term><option>disconnect</option></term>
@@ -795,14 +793,14 @@
<varlistentry><term><option>violently</option></term>
<listitem><para>
Sync to the primary node is allowed, violating the
- assumption that data on a block device is stable for one
+ assumption that data on a block device are stable for one
of the nodes. DANGEROUS, DO NOT USE.
</para></listitem></varlistentry>
<varlistentry><term><option>call-pri-lost</option></term>
<listitem><para>
Call the "pri-lost" helper program on one of the
machines. This program is expected to reboot the
- machine. (I.e. make it secondary.)
+ machine, i.e. make it secondary.
</para></listitem></varlistentry>
</variablelist>
</listitem>
@@ -815,10 +813,10 @@
The init script <citerefentry><refentrytitle>drbd</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> blocks the boot process
until the DRBD resources are connected.
- This is so when the cluster manager starts later,
+ When the cluster manager starts later,
it does not see a resource with internal split-brain.
In case you want to limit the wait time, do it here.
- Default is 0, which means unlimited. Unit is seconds.
+ Default is 0, which means unlimited. The unit is seconds.
</para></listitem>
</varlistentry>
@@ -831,7 +829,7 @@
is rebooted, this timeout value is used instead of wfc-timeout,
because the peer is less likely to show up in time,
if it had been dead before.
- Default is 60, unit is seconds. Value 0 means unlimited.
+ The default value is 60, the unit is seconds. Value 0 means unlimited.
</para>
</listitem>
</varlistentry>
@@ -840,9 +838,9 @@
<term><option>rate <replaceable>rate</replaceable></option></term>
<listitem><para>
<indexterm><primary>drbd.conf</primary><secondary>rate </secondary></indexterm>
- To ensure smooth operation of the application on top of DRBD,
+ To ensure a smooth operation of the application on top of DRBD,
it is possible to limit the bandwidth which may be used by
- background synchronizations. The default is 250 KB/sec, the
+ background synchronisations. The default is 250 KB/sec, the
default unit is KB/sec. Optional suffixes K, M, G are allowed.
</para>
</listitem>
@@ -852,10 +850,10 @@
<term><option>after <replaceable>res-name</replaceable></option></term>
<listitem><para>
<indexterm><primary>drbd.conf</primary><secondary>after </secondary></indexterm>
- By default resynchronization of all devices would run in parallel.
- By defining an sync-after dependency the resynchronisation of this
- resource will start only if the resoruce <replaceable>res-name</replaceable>
- is already in connected state (=finished its resynchronisation).
+ By default, resynchronisation of all devices would run in parallel.
+ By defining a sync-after dependency, the resynchronisation of this
+ resource will start only if the resource <replaceable>res-name</replaceable>
+ is already in connected state (= finished its resynchronisation).
</para></listitem>
</varlistentry>
@@ -863,10 +861,10 @@
<term><option>al-extents <replaceable>extents</replaceable></option></term>
<listitem><para>DRBD automatically performs hot area detection. With this
<indexterm><primary>drbd.conf</primary><secondary>al-extents </secondary></indexterm>
- parameter you control how big the hot area (=active set) can
- get. Each extent marks 4M of the backing storage (=low level device).
- In case a primary node leaves the cluster unexpectedly the areas covered
- by the active set must be resynced upon rejoin of the failed
+ parameter you control how big the hot area (= active set) can
+ get. Each extent marks 4M of the backing storage (= low-level device).
+ In case a primary node leaves the cluster unexpectedly, the areas covered
+ by the active set must be resynced upon rejoining of the failed
node. The data structure is stored in the meta-data area, therefore each
change of the active set is a write operation
to the meta-data device. A higher number of extents gives
@@ -881,22 +879,22 @@
<term><option>pri-on-incon-degr <replaceable>cmd</replaceable></option></term>
<listitem><para> This handler is called if the node is primary, degraded
<indexterm><primary>drbd.conf</primary><secondary>pri-on-incon-degr </secondary></indexterm>
- and the local copy of the data is inconsistent.</para></listitem>
+ and if the local copy of the data is inconsistent.</para></listitem>
</varlistentry>
<varlistentry>
<term><option>pri-lost-after-sb <replaceable>cmd</replaceable></option></term>
<listitem><para> The node is currently primary, but lost the after split
<indexterm><primary>drbd.conf</primary><secondary>pri-lost-after-sb </secondary></indexterm>
- brain auto recovery procedure. As as consequence it should go away.
+ brain auto recovery procedure. As as consequence, it should be abandoned.
</para></listitem> </varlistentry>
<varlistentry>
<term><option>pri-lost <replaceable>cmd</replaceable></option></term>
<listitem><para> The node is currently primary, but DRBD's algorithm
<indexterm><primary>drbd.conf</primary><secondary>pri-lost </secondary></indexterm>
- thinks, that it should become sync target, as consequence it should
- give up its primary state.
+ thinks that it should become sync target. As a consequence it should
+ give up its primary role.
</para></listitem> </varlistentry>
<varlistentry>
@@ -904,7 +902,7 @@
<listitem><para> The handler is part of the <option>fencing</option>
<indexterm><primary>drbd.conf</primary><secondary>outdate-peer </secondary></indexterm>
mechanism. This handler is called in case the node needs to outdate the
- peer's disk. It should use other communication pathes then DRBD's network
+ peer's disk. It should use other communication paths than DRBD's network
link. </para></listitem> </varlistentry>
<varlistentry>
Modified: trunk/documentation/drbdadm.sgml
===================================================================
--- trunk/documentation/drbdadm.sgml 2007-05-04 20:56:17 UTC (rev 2869)
+++ trunk/documentation/drbdadm.sgml 2007-05-06 20:02:07 UTC (rev 2870)
@@ -89,7 +89,7 @@
<term>detach</term>
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>detach</secondary></indexterm>
- Removes the backing storage device from a DRBD resources's device.
+ Removes the backing storage device from a DRBD resource's device.
</para></listitem>
</varlistentry>
<varlistentry>
@@ -105,14 +105,14 @@
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>disconnect</secondary></indexterm>
Removes the network configuration from the resource. The device
- will go into StandAllone state.
+ will go into StandAlone state.
</para></listitem>
</varlistentry>
<varlistentry>
<term>syncer</term>
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>syncer</secondary></indexterm>
- Loads the resynchronization parameters into the device.
+ Loads the resynchronisation parameters into the device.
</para></listitem>
</varlistentry>
<varlistentry>
@@ -134,16 +134,16 @@
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>primary</secondary></indexterm>
Switch the resource's device into primary state. You need to do
- this before you may mount a filesystem onto the device.
+ this before you mount a filesystem onto the device.
</para></listitem>
</varlistentry>
<varlistentry>
<term>secondary</term>
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>secondary</secondary></indexterm>
- Brings the device back into secondary state. This is needed since in
- a connected DRBD device pair there might only be one of the two peers
- in primary state.
+ Brings the device back into secondary role. This is needed since in
+ a connected DRBD device pair, only one of the two peers may have
+ primary role.
</para></listitem>
</varlistentry>
<varlistentry>
@@ -151,7 +151,7 @@
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>invalidate</secondary></indexterm>
This forces DRBD to consider the data on the local backing
- storage device as out-of-sync. Therefor DRBD will copy each
+ storage device as out-of-sync. Therefore DRBD will copy each
and every block over from its peer, to bring the local storage
device back in sync.
</para></listitem>
@@ -160,7 +160,7 @@
<term>invalidate_remote</term>
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>invalidate_remote</secondary></indexterm>
- This command is similar to the invalidate command, but the
+ This command is similar to the invalidate command, however, the
backing storage of the peer is invalidated and hence rewritten
with the data of the local node.
</para></listitem>
@@ -169,7 +169,7 @@
<term>resize</term>
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>resize</secondary></indexterm>
- DRBD will reexamine all sizing constraints, and re-size the
+ DRBD will reexamine all sizing constraints, and resize the
resource's device accordingly. E.g. in case you increased the
size of your backing storage devices (on both nodes of course),
then DRBD will adopt to the new size after you called
@@ -180,7 +180,7 @@
<term>create-md</term>
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>create-md</secondary></indexterm>
- Create-md initializes the meta data storage. This needs to be
+ Create-md initialises the meta data storage. This needs to be
done before a DRBD resource can be taken online for the first
time.
</para></listitem>
@@ -190,7 +190,7 @@
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>get-gi</secondary></indexterm>
Get-gi shows a short textual repesentation of the data generation
- identifier.
+ identifiers.
</para></listitem>
</varlistentry>
<varlistentry>
@@ -205,7 +205,7 @@
<term>dump-md</term>
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>dump-md</secondary></indexterm>
- Dumps the whole contents of the meta data storage including
+ Dumps the whole contents of the meta data storage, including
the stored bit-map and activity-log, in a textual representation.
</para></listitem>
</varlistentry>
@@ -220,7 +220,7 @@
<term>adjust</term>
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>adjust</secondary></indexterm>
- Synchronizes the configuration of device with your configuration
+ Synchronises the configuration of the device with your configuration
file. You should always examine the output of the dry-run
mode before actually executing this command.
</para></listitem>
@@ -244,14 +244,14 @@
<term>cstate</term>
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>cstate</secondary></indexterm>
- Shows the current connection status of the devices.
+ Shows the current connection state of the devices.
</para></listitem>
</varlistentry>
<varlistentry>
<term>dump</term>
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>dump</secondary></indexterm>
- Just parse the configuration file and dump it to stdout. Might
+ Just parse the configuration file and dump it to stdout. May
be used to check the configuration file for syntactical correctness.
</para></listitem>
</varlistentry>
@@ -270,7 +270,7 @@
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>pause-sync</secondary></indexterm>
Temporarily suspend an ongoing resynchronisation by setting the
- local pause flag. Resync only progresses if neighter the local
+ local pause flag. Resync only progresses if neither the local
nor the remote pause flag is set. It might be desirable to
postpone DRBD's resynchronisation after eventual
resynchronisation of the backing storage's RAID setup.
@@ -289,14 +289,14 @@
<term>dstate</term>
<listitem><para>
<indexterm><primary>drbdadm</primary><secondary>dstate</secondary></indexterm>
- Show the current state of the backing storeage devices. (local/peer)
+ Show the current state of the backing storage devices. (local/peer)
</para></listitem>
</varlistentry>
<varlistentry>
<term>hidden-commands</term>
<listitem><para>
- Shows all on purpose undocumented commands.
+ Shows all commands undocumented on purpose.
</para></listitem>
</varlistentry>
Modified: trunk/documentation/drbddisk.sgml
===================================================================
--- trunk/documentation/drbddisk.sgml 2007-05-04 20:56:17 UTC (rev 2869)
+++ trunk/documentation/drbddisk.sgml 2007-05-06 20:02:07 UTC (rev 2870)
@@ -31,7 +31,7 @@
The <option>/etc/ha.d/resource.d/drbddisk</option> script
brings the local device of <replaceable>resource</replaceable> into
primary state. It is designed to be
- used by heartbeat.
+ used by Heartbeat.
</para>
<para>
In order to use <option>/etc/ha.d/resource.d/drbddisk</option> you must
Modified: trunk/documentation/drbdmeta.sgml
===================================================================
--- trunk/documentation/drbdmeta.sgml 2007-05-04 20:56:17 UTC (rev 2869)
+++ trunk/documentation/drbdmeta.sgml 2007-05-06 20:02:07 UTC (rev 2870)
@@ -32,12 +32,12 @@
<para>
Drbdmeta is used to create, display and modify the contents of
DRBD's meta data storage. Usually you do not want to use this
- command directly but use it through the front end drbdadm.
+ command directly, but use it through the front end drbdadm.
</para>
<para>
This command only works if the DRBD resource is currently down,
or at least detached from its backing stoage. The first parameter
- is the device node assosiated to the resource. With the second
+ is the device node associated to the resource. With the second
parameter you select which the version of the meta data. Currently
all major DRBD releases (0.6, 0.7 and 0.8) are supported.
</para>
@@ -49,7 +49,7 @@
<term>create-md</term>
<listitem><para>
<indexterm><primary>drbdmeta</primary><secondary>create-md</secondary></indexterm>
- Create-md initializes the meta data storage. This needs to be
+ Create-md initialises the meta data storage. This needs to be
done before a DRBD resource can be taken online for the first
time. In case there is already a meta data signature of an
older format in place, drbdmeta will ask you if it should
@@ -61,8 +61,8 @@
<listitem><para>
<indexterm><primary>drbdmeta</primary><secondary>get-gi</secondary></indexterm>
Get-gi shows a short textual repesentation of the data generation
- identifier. In version 0.6 and 0.7 this are generation counters,
- while in version 0.8 this is a set of UUIDs.
+ identifier. In version 0.6 and 0.7 these are generation counters,
+ while in version 0.8 it is a set of UUIDs.
</para></listitem>
</varlistentry>
<varlistentry>
@@ -86,7 +86,7 @@
<listitem><para>
<indexterm><primary>drbdmeta</primary><secondary>outdate</secondary></indexterm>
Sets the outdated flag in the meta data. This is used by the
- peer node when it wants to become primary, but can not reach
+ peer node when it wants to become primary, but cannot
communicate with the DRBD stack on this host.
</para></listitem>
</varlistentry>
@@ -94,7 +94,7 @@
<term>dstate</term>
<listitem><para>
<indexterm><primary>drbdmeta</primary><secondary>dstate</secondary></indexterm>
- Prints the state of the backing storag's data. The output
+ Prints the state of the data on the backing storage. The output
is always followed by '/DUnknown' since drbdmeta only looks
at the local meta data.
</para></listitem>
@@ -106,10 +106,10 @@
<title>Expert's commands</title>
<para>
Drbdmeta allows you to modifiy the meta data as well. This is
- intetionally omitted for the commad's usage output, since you
- should only use this if you really know what you are doing.
- By setting the generation identifiers to wrong values you
- risk to overwrite your up-to-data data by an older version
+ intentionally omitted for the command's usage output, since you
+ should only use it if you really know what you are doing.
+ By setting the generation identifiers to wrong values, you
+ risk to overwrite your up-to-data data with an older version
of your data.
</para>
<variablelist>
@@ -128,7 +128,7 @@
<listitem><para>
<indexterm><primary>drbdmeta</primary><secondary>restore-md </secondary></indexterm>
Reads the <replaceable>dump_file</replaceable> and writes
- the it to the meta data.
+ it to the meta data.
</para></listitem>
</varlistentry>
</variablelist>
Modified: trunk/documentation/drbdsetup.sgml
===================================================================
--- trunk/documentation/drbdsetup.sgml 2007-05-04 20:56:17 UTC (rev 2869)
+++ trunk/documentation/drbdsetup.sgml 2007-05-06 20:02:07 UTC (rev 2870)
@@ -198,7 +198,7 @@
<title>Note</title>
<para>
drbdsetup is a low level tool of the DRBD program suite. It is
- used by the datadisk and drbd scripts to communicate with
+ used by the data disk and drbd scripts to communicate with
the device driver.
</para>
</refsect1>
@@ -251,7 +251,7 @@
The <option>-d</option> (or <option>--disk-size</option>) should
only be used if you wish not to use as much as possible from the
backing block devices.
- If you do not use <option>-d</option> the <replaceable>device</replaceable>
+ If you do not use <option>-d</option>, the <replaceable>device</replaceable>
is only ready for use as soon as it was connected to its peer once.
(See the <option>net</option> command.)
</para>
@@ -278,9 +278,9 @@
If the driver of the <replaceable>lower_device</replaceable>
reports an error to DRBD, DRBD will either pass the error
to the upper layers of the operating system, call a helper
- program, or detaches the device from its backing storage and
+ program, or detach the device from its backing storage and
perform all futher IO by requesting it from the peer. The
- valid <replaceable>err_handler</replaceable> are:
+ valid <replaceable>err_handlers</replaceable> are:
<option>pass_on</option>, <option>call-local-io-error</option>
and <option>detach</option>.
</para>
@@ -306,21 +306,21 @@
</para></listitem></varlistentry>
<varlistentry><term><option>resource-only</option></term>
<listitem><para>
- If a node becomes a disconnected primary it tries to outdate
+ If a node becomes a disconnected primary. it tries to outdate
the peer's disk. This is done by calling the outdate-peer
handler. The handler is supposed to reach the other node over
- alternative communication pathes and call 'drbdadm outdate
+ alternative communication paths and call 'drbdadm outdate
res' there.
</para></listitem></varlistentry>
<varlistentry><term><option>resource-and-stonith</option></term>
<listitem><para>
- If a node becomes a disconnected primary it freezes all
+ If a node becomes a disconnected primary, it freezes all
its IO operations and calls its outdate-peer handler. The
- outdate-peer hander is supposed to reach the peer over
- alternative communicaton pathes and call 'drbdadm outdate
- res' there. In case it can not reach the peer it should
+ outdate-peer handler is supposed to reach the peer over
+ alternative communicaton paths and call 'drbdadm outdate
+ res' there. In case it cannot reach the peer, it should
stonith the peer. IO is resumed as soon as the situation
- is resolved. In case your handler fails you can resume
+ is resolved. In case your handler fails, you can resume
IO with the <option>resume-io</option> command.
</para></listitem></varlistentry>
</variablelist>
@@ -332,18 +332,19 @@
<listitem>
<para>
In case the backing storage's driver has a merge_bvec_fn()
- function (At time of writing the only known drivers which
- have such a function are: md (software raid driver),
- dm (device mapper - LVM) and DRBD itself) drbd has to
+ function, DRBD has to
pretend that it can only process IO requests in units
- not lager than 4kByte.</para>
+ not lager than 4kByte. (At time of writing the only known
+ drivers which
+ have such a function are: md (software raid driver),
+ dm (device mapper - LVM) and DRBD itself)</para>
<para>
To get best performance out of DRBD on top of software
raid (or any other driver with a merge_bvec_fn() function)
- you might enable this function, iff you know for sure
+ you might enable this function, if you know for sure
that the merge_bvec_fn() function will deliver the same
results on all nodes of your cluster. I.e. the physical
- disks of the software raid are of the exact same type.
+ disks of the software raid are exactly of the same type.
USE THIS OPTION ONLY IF YOU KNOW WHAT YOU ARE DOING.</para>
</listitem>
</varlistentry>
@@ -388,7 +389,7 @@
If the TCP/IP connection linking a DRBD device pair is idle
for more than <replaceable>time</replaceable> seconds, DRBD
will generate a keep-alive packet to check if its partner is
- still alive. The default is 10 seconds, the unit is 1 second.
+ still alive. The default value is 10 seconds, the unit is 1 second.
</para>
</listitem>
</varlistentry>
@@ -401,7 +402,7 @@
within <replaceable>val</replaceable>
10<superscript>ths</superscript> of a second, the partner node
is considered dead and therefore the TCP/IP connection is
- abandoned. The default value is 60 = 6 seconds.
+ abandoned. The default value is 60 (= 6 seconds).
</para>
</listitem>
</varlistentry>
@@ -418,7 +419,7 @@
and secondary nodes. But keep in mind that more asynchronism
is synonymous with more data loss in the case of a primary
node failure. The default <replaceable>size</replaceable> is
- 128 KB. Default unit is KB.
+ 128 KB, the default unit is KB.
</para>
</listitem>
</varlistentry>
@@ -442,8 +443,8 @@
<para>
With this option the maximal number of write requests between
two barriers is limited. Should be set to the same as
- <option>--max-buffers </option>. Values smaller then 100 can
- lead to degraded performace. The default is 2048.
+ <option>--max-buffers </option>. Values smaller than 100 can
+ lead to degraded performance. The default value is 2048.
</para>
</listitem>
</varlistentry>
@@ -455,7 +456,7 @@
With this option the maximal number of buffer pages allocated
by DRBD's receiver thread is limited. Should be set to the
same as <option>--max-epoch-size </option>. Small values
- could lead to degraded performace. (Minimum 32) The default is
+ could lead to degraded performance. (Minimum 32) The default value is
2048.
</para>
</listitem>
@@ -469,7 +470,7 @@
(secondary) node exceeds the unplug-watermark, we trigger
the request processing of our backing storage device.
Some storage controllers deliver better performance with small
- values, other deliver best performance when it is set to
+ values, others deliver best performance when the value is set to
the same value as max-buffers. Minimum 16, default 128, maximum
131072.
</para>
@@ -480,11 +481,11 @@
<option>--allow-two-primaries </option></term>
<listitem>
<para>
- With this option set you might make both nodes primary. You
- only should use this options if you use a shared storage
+ With this option set you may assign primary role to both nodes. You
+ only should use this option if you use a shared storage
file system on top of DRBD. At the time of writing the only
ones are: OCFS2 and GFS. If you use this option with any
- other filesystem you are goint to crash your nodes and to
+ other file system, you are going to crash your nodes and to
corrupt your data!
</para>
</listitem>
@@ -494,11 +495,11 @@
<option>--cram-hmac-alg </option><replaceable>alg</replaceable></term>
<listitem>
<para>
- You need to specifying the HMAC algorithm to enable peer
- authentication at all. It is strongly enouraged to use
+ You need to specify the HMAC algorithm to enable peer
+ authentication at all. You are strongly enouraged to use
peer authentication.
- The HMAC algorithm which will be used for the challenge
- response authentication of the peer. You might specify any
+ The HMAC algorithm will be used for the challenge
+ response authentication of the peer. You may specify any
digest algorithm that is named in /proc/crypto.
</para>
</listitem>
@@ -527,13 +528,12 @@
</para></listitem></varlistentry>
<varlistentry><term><option>discard-younger-primary</option></term>
<listitem><para>
- Auto sync from the node that was primary before the split
- brain situation happened.
+ Auto sync from the node that was primary before the split- brain situation occurred.
</para></listitem></varlistentry>
<varlistentry><term><option>discard-older-primary</option></term>
<listitem><para>
Auto sync from the node that became primary as second during
- the split brain situation.
+ the split-brain situation.
</para></listitem></varlistentry>
<varlistentry><term><option>discard-zero-changes</option></term>
<listitem><para>
@@ -573,7 +573,7 @@
<varlistentry><term><option>consensus</option></term>
<listitem><para>
Discard the version of the secondary if the outcome
- if the <option>after-sb-0pri</option> algorithm would also
+ of the <option>after-sb-0pri</option> algorithm would also
destroy the current secondary's data. Otherwise disconnect.
</para></listitem></varlistentry>
<varlistentry><term><option>discard-secondary</option></term>
@@ -583,14 +583,14 @@
<varlistentry><term><option>call-pri-lost-after-sb</option></term>
<listitem><para>
Always honour the outcome of the <option>after-sb-0pri
- </option> algorithm. In case it decides the the current
+ </option> algorithm. In case it decides the current
secondary has the right data, call the
<option>pri-lost-after-sb</option> on the current primary.
</para></listitem></varlistentry>
<varlistentry><term><option>violently-as0p</option></term>
<listitem><para>
Always honour the outcome of the <option>after-sb-0pri
- </option> algorithm. In case it decides the the current
+ </option> algorithm. In case it decides the current
secondary has the right data, accept a possible instantaneous
change of the primary's data.
</para></listitem></varlistentry>
@@ -613,14 +613,14 @@
<varlistentry><term><option>call-pri-lost-after-sb</option></term>
<listitem><para>
Always honour the outcome of the <option>after-sb-0pri
- </option> algorithm. In case it decides the the current
+ </option> algorithm. In case it decides the current
secondary has the right data, call the
<option>pri-lost-after-sb</option> on the current primary.
</para></listitem></varlistentry>
<varlistentry><term><option>violently-as0p</option></term>
<listitem><para>
Always honour the outcome of the <option>after-sb-0pri
- </option> algorithm. In case it decides the the current
+ </option> algorithm. In case it decides the current
secondary has the right data, accept a possible instantaneous
change of the primary's data.
</para></listitem></varlistentry>
@@ -634,15 +634,15 @@
<listitem>
<para>
Normally the automatic after-split-brain policies are only
- used if current state of the UUIDs do not indicate the
+ used if current states of the UUIDs do not indicate the
presence of a third node.
</para>
<para>
With this option you request that the automatic
after-split-brain policies are used as long as the data
sets of the nodes are somehow related. This might cause
- a full sync, if the UUIDs indicates the presence of a third
- node. (Or double faults led to strange UUID sets.)
+ a full sync, if the UUIDs indicate the presence of a third
+ node. (Or double faults have led to strange UUID sets.)
</para>
</listitem>
</varlistentry>
@@ -659,16 +659,16 @@
<option>call-pri-lost</option> and
<option>violently</option>. While <option>disconnect</option>
speaks for itself, with the <option>call-pri-lost</option>
- setting the <option>pri-lost</option> handler gets called
- witch is expeced to either change the role of the node to
+ setting the <option>pri-lost</option> handler is called
+ which is expected to either change the role of the node to
secondary, or remove the node from the cluster.
The default is <option>disconnect</option>.</para>
<para>
With the <option>violently</option> setting you allow DRBD
to force a primary node into SyncTarget state. This means
- that with that action the data exposed by DRBD changes to
- the SyncSource's version of the data instantaneous.
- USE THIS ONLY IF YOU KNOW WHAT YOU ARE DOING.
+ that with that action the data exposed by DRBD change to
+ the SyncSource's version of the data instantaneously.
+ USE THIS OPTION ONLY IF YOU KNOW WHAT YOU ARE DOING.
</para>
</listitem>
</varlistentry>
@@ -678,9 +678,8 @@
<option>--ping-timeout </option><replaceable>ping_timeout</replaceable></term>
<listitem>
<para>
- The time the peer has time to answer to a keep-alive packet,
- it. In case the peer's reply is not received within this
- time period, it is considered as dead. The default is 500ms,
+ The time the peer has to answer to a keep-alive packet. In case the peer's reply is not received within this
+ time period, it is considered as dead. The default value is 500ms,
the default unit is 100ms.
</para>
</listitem>
@@ -691,11 +690,10 @@
<option>--discard-my-data </option></term>
<listitem>
<para>
- Use this option to manually recover from a split brain
- situation. In case you do not have any automatic after
- split brain policies selected, the nodes refuse to
+ Use this option to manually recover from a split-brain
+ situation. In case you do not have any automatic after-split-brain policies selected, the nodes refuse to
connect. By passing this option you make a node to
- sync target immediatly after sucessfull connect.
+ sync target immediately after sucessful connect.
</para>
</listitem>
</varlistentry>
@@ -706,7 +704,7 @@
<title>syncer</title>
<indexterm><primary>drbdsetup</primary><secondary>syncer</secondary></indexterm>
<para>
- Changes the synchronization daemon parameters of
+ Changes the synchronisation daemon parameters of
<replaceable>device</replaceable> at runtime.
</para>
<variablelist>
@@ -716,8 +714,8 @@
<listitem>
<para>
To ensure smooth operation of the application on top of DRBD,
- it is possible to limit the bandwidth which may be used by
- background synchronizations. The default is 250 KB/sec, the
+ it is possible to limit the bandwidth that may be used by
+ background synchronisation. The default is 250 KB/sec, the
default unit is KB/sec.
</para>
</listitem>
@@ -729,7 +727,7 @@
<para>
Start resync on this device only if the device with
<replaceable>minor</replaceable> is already in connected
- state. Other wise this device wait in SyncPause state.
+ state. Otherwise this device waits in SyncPause state.
</para>
</listitem>
</varlistentry>
@@ -741,8 +739,8 @@
DRBD automatically performs hot area detection. With this
parameter you control how big the hot area (=active set) can
get. Each extent marks 4M of the backing storage. In case a
- primary node leaves the cluster unexpectedly the areas covered
- by the active set must be resynced upon rejoin of the failed
+ primary node leaves the cluster unexpectedly, the areas covered
+ by the active set must be resynced upon rejoining of the failed
node. The data structure is stored in the meta-data area,
therefore each change of the active set is a write operation
to the meta-data device. A higher number of extents gives
@@ -758,15 +756,15 @@
<title>primary</title>
<indexterm><primary>drbdsetup</primary><secondary>primary</secondary></indexterm>
<para>
- Sets the <replaceable>device</replaceable> into primary state, this
+ Sets the <replaceable>device</replaceable> into primary role. This
means that applications (e.g. a file system) may open the
<replaceable>device</replaceable> for read and write access. Data
- written to the <replaceable>device</replaceable> in primary state is
- mirrored to the device in secondary state.
+ written to the <replaceable>device</replaceable> in primary role are
+ mirrored to the device in secondary role.
</para>
<para>
It is not possible to set both devices of a connected DRBD device
- pair to primary state.
+ pair to primary role.
</para>
<variablelist>
<varlistentry>
@@ -834,11 +832,11 @@
<listitem>
<para>
This command will fail if the
- <replaceable>device</replaceable> can not communicate with its
+ <replaceable>device</replaceable> cannot communicate with its
partner for <replaceable>timeout</replaceable>
- seconds. If the peer was working before this node got
- rebootet, the wfc_timeout is used. If the peer was already
- down before this node got rebooted, the degr_wfc_timeout
+ seconds. If the peer was working before this node was
+ rebooted, the wfc_timeout is used. If the peer was already
+ down before this node was rebooted, the degr_wfc_timeout
is used.
The default value for <replaceable>wfc_timeout</replaceable>
is 0 which means to wait forever. The default for
@@ -853,7 +851,7 @@
<indexterm><primary>drbdsetup</primary><secondary>wait_sync</secondary></indexterm>
<para>
Returns as soon as the <replaceable>device</replaceable> leaves any
- synchronization state and returns into connected state. The options
+ synchronisation into connected state. The options
are the same as with the <replaceable>wait_connect</replaceable>
command.
</para>
@@ -865,7 +863,7 @@
Removes the information set by the <option>net</option> command
from the <replaceable>device</replaceable>. This means
that the <replaceable>device</replaceable> goes into unconnected
- state and that it will no longer listen for incoming connections.
+ state and will no longer listen for incoming connections.
</para>
</refsect2>
<refsect2>
@@ -899,7 +897,7 @@
<title>cstate</title>
<indexterm><primary>drbdsetup</primary><secondary>cstate</secondary></indexterm>
<para>
- Shows the current connection states of the
+ Shows the current connection state of the
<replaceable>device</replaceable>.
</para>
</refsect2>
@@ -907,7 +905,7 @@
<title>dstate</title>
<indexterm><primary>drbdsetup</primary><secondary>dstate</secondary></indexterm>
<para>
- Show the current state of the backing storeage devices. (local/peer)
+ Shows the current states of the backing storage devices. (local/peer)
</para>
</refsect2>
<refsect2>
@@ -926,7 +924,7 @@
<indexterm><primary>drbdsetup</primary><secondary>pause-sync</secondary></indexterm>
<para>
Temporarily suspend an ongoing resynchronisation by setting the local
- pause flag. Resync only progresses if neighter the local nor the
+ pause flag. Resync only progresses if neither the local nor the
remote pause flag is set. It might be desirable to postpone DRBD's
resynchronisation after eventual resynchronisation of the backing
storage's RAID setup.
@@ -952,14 +950,14 @@
<title>show-gi</title>
<indexterm><primary>drbdsetup</primary><secondary>show-gi</secondary></indexterm>
<para>
- Displays the device's data generaion identifiers verbosily.
+ Displays the device's data generation identifiers verbosely.
</para>
</refsect2>
<refsect2>
<title>get-gi</title>
<indexterm><primary>drbdsetup</primary><secondary>get-gi</secondary></indexterm>
<para>
- Displays the device's data generaion identifiers.
+ Displays the device's data generation identifiers.
</para>
</refsect2>
<refsect2>
@@ -982,7 +980,7 @@
<title>resume-io</title>
<indexterm><primary>drbdsetup</primary><secondary>resume-io</secondary></indexterm>
<para>
- In the the outdate-peer handler fails to stonith the peer node,
+ If the outdate-peer handler fails to stonith the peer node,
and your <option>fencing</option> policy is set to
resource-and-stonith, you can unfreeze IO operations with this
command.
@@ -994,8 +992,8 @@
<indexterm><primary>drbdsetup</primary><secondary>events</secondary></indexterm>
<para>
Displays every state change of DRBD and all calls to helper
- programs. This might be used to get notifies of DRBD's state
- changes by piping the output to an other program.
+ programs. This might be used to get notified of DRBD's state
+ changes by piping the output to another program.
<variablelist>
<varlistentry>
@@ -1013,7 +1011,7 @@
<option>--unfiltered</option></term>
<listitem>
<para>
- This is an debugging aid, and displays the content of
+ This is a debugging aid that displays the content of
all received netlink messages.
</para>
</listitem>
@@ -1026,7 +1024,7 @@
<refsect1>
<title>Examples</title>
<para>
- For examples please have a look at the
+ For examples, please have a look at the
<ulink url="http://www.linux-ha.org/DRBD/QuickStart07">
<citetitle>DRBD Quickstart Guide</citetitle></ulink>.
</para>
More information about the drbd-cvs
mailing list