X-Git-Url: https://git.whamcloud.com/?a=blobdiff_plain;f=UnderstandingFailover.xml;h=7ff66d3482e46609e9ba5f7f2ef69a6d56d15472;hb=e096f06b81ed50da7c6f21867162f272299465ef;hp=ef215cc42d9295d2b82a5a58a5a0aa3f3a520670;hpb=bfc3782667e73a23f28a7b9cac0df416e9b575b0;p=doc%2Fmanual.git

diff --git a/UnderstandingFailover.xml b/UnderstandingFailover.xml
index ef215cc..7ff66d3 100644
--- a/UnderstandingFailover.xml
+++ b/UnderstandingFailover.xml
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='utf-8'?>
 <chapter xmlns="http://docbook.org/ns/docbook"
-xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en-US"
-xml:id="understandingfailover">
+ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en-US"
+ xml:id="understandingfailover">
   <title xml:id="understandingfailover.title">Understanding Failover in a
   Lustre File System</title>
   <para>This chapter describes failover in a Lustre file system. It
@@ -105,28 +105,26 @@ xml:id="understandingfailover">
       <itemizedlist>
         <listitem>
           <para>
-          <emphasis role="bold">Active/passive</emphasis>pair - In this
+          <emphasis role="bold">Active/passive</emphasis> pair - In this
           configuration, the active node provides resources and serves data,
           while the passive node is usually standing by idle. If the active
           node fails, the passive node takes over and becomes active.</para>
         </listitem>
         <listitem>
           <para>
-          <emphasis role="bold">Active/active</emphasis>pair - In this
+          <emphasis role="bold">Active/active</emphasis> pair - In this
           configuration, both nodes are active, each providing a subset of
           resources. In case of a failure, the second node takes over resources
           from the failed node.</para>
         </listitem>
       </itemizedlist>
-      <para>In Lustre software releases previous to Lustre software release
-      2.4, MDSs can be configured as an active/passive pair, while OSSs can be
-      deployed in an active/active configuration that provides redundancy
+      <para>If there is a single MDT in a filesystem, two MDSes can be
+      configured as an active/passive pair, while pairs of OSSes can be
+      deployed in an active/active configuration that improves OST availability
       without extra overhead. Often the standby MDS is the active MDS for
       another Lustre file system or the MGS, so no nodes are idle in the
-      cluster.</para>
-      <para condition="l24">Lustre software release 2.4 introduces metadata
-      targets for individual sub-directories. Active-active failover
-      configurations are available for MDSs that serve MDTs on shared
+      cluster.  If there are multiple MDTs in a filesystem, active-active
+      failover configurations are available for MDSs that serve MDTs on shared
       storage.</para>
     </section>
   </section>
@@ -149,11 +147,10 @@ xml:id="understandingfailover">
     <itemizedlist>
       <listitem>
         <para>For MDT failover, two MDSs can be configured to serve the same
-        MDT. Only one MDS node can serve an MDT at a time.</para>
-        <para condition="l24">Lustresoftware release 2.4 allows multiple MDTs.
-        By placing two or more MDT partitions on storage shared by two MDSs,
-        one MDS can fail and the remaining MDS can begin serving the unserved
-        MDT. This is described as an active/active failover pair.</para>
+          MDT. Only one MDS node can serve any MDT at one time.
+          By placing two or more MDT devices on storage shared by two MDSs,
+          one MDS can fail and the remaining MDS can begin serving the unserved
+          MDT. This is described as an active/active failover pair.</para>
       </listitem>
       <listitem>
         <para>For OST failover, multiple OSS nodes can be configured to be able
@@ -170,8 +167,8 @@ xml:id="understandingfailover">
     active (using 
     <literal>tunefs.lustre</literal>). For explanations of these utilities, see
     
-    <xref linkend="dbdoclet.50438219_75432" />and 
-    <xref linkend="dbdoclet.50438219_39574" />.</para>
+    <xref linkend="mkfs.lustre" />and 
+    <xref linkend="tunefs.lustre" />.</para>
     <para>Failover capability in a Lustre file system can be used to upgrade
     the Lustre software between successive minor versions without cluster
     downtime. For more information, see 
@@ -210,9 +207,8 @@ xml:id="understandingfailover">
         configured in a quasi active/active configuration, with each MDS
         managing metadata for a subset of the Lustre file system.</para>
       </note>
-      <figure>
-        <title xml:id="understandingfailover.fig.configmdt">Lustre failover
-        configuration for a active/passive MDT</title>
+      <figure xml:id="understandingfailover.fig.configmdt">
+        <title>Lustre failover configuration for a active/passive MDT</title>
         <mediaobject>
           <imageobject>
             <imagedata fileref="./figures/MDT_Failover.png" />
@@ -223,19 +219,17 @@ xml:id="understandingfailover">
         </mediaobject>
       </figure>
     </section>
-    <section xml:id='dbdoclet.mdtactiveactive' condition='l24'>
+    <section xml:id='dbdoclet.mdtactiveactive'>
       <title>
       <indexterm>
         <primary>failover</primary>
         <secondary>MDT</secondary>
       </indexterm>MDT Failover Configuration (Active/Active)</title>
-      <para>Multiple MDTs became available with the advent of Lustre software
-      release 2.4. MDTs can be setup as an active/active failover
+      <para>MDTs can be configured as an active/active failover
       configuration. A failover cluster is built from two MDSs as shown in 
       <xref linkend="understandingfailover.fig.configmdts" />.</para>
-      <figure>
-        <title xml:id="understandingfailover.fig.configmdts">Lustre failover
-        configuration for a active/active MDTs</title>
+      <figure xml:id="understandingfailover.fig.configmdts">
+        <title>Lustre failover configuration for a active/active MDTs</title>
         <mediaobject>
           <imageobject>
             <imagedata scalefit="1" width="50%"
@@ -261,9 +255,8 @@ xml:id="understandingfailover">
         <para>OSSs configured as a failover pair must have shared
         disks/RAID.</para>
       </note>
-      <figure>
-        <title xml:id="understandingfailover.fig.configost">Lustre failover
-        configuration for an OSTs</title>
+      <figure xml:id="understandingfailover.fig.configost">
+        <title>Lustre failover configuration for an OSTs</title>
         <mediaobject>
           <imageobject>
             <imagedata scalefit="1" width="100%"
@@ -288,3 +281,6 @@ xml:id="understandingfailover">
     </section>
   </section>
 </chapter>
+<!--
+  vim:expandtab:shiftwidth=2:tabstop=8:
+  -->