Whamcloud - gitweb
LUDOC-522 Nodemap: Added nodemap_del examples.
[doc/manual.git] / TroubleShootingRecovery.xml
index 85b9ceb..b9c97ce 100644 (file)
@@ -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="troubleshootingrecovery">
+ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en-US"
+ xml:id="troubleshootingrecovery">
   <title xml:id="troubleshootingrecovery.title">Troubleshooting
   Recovery</title>
   <para>This chapter describes what to do if something goes wrong during
@@ -9,26 +9,26 @@ xml:id="troubleshootingrecovery">
   <itemizedlist>
     <listitem>
       <para>
-        <xref linkend="dbdoclet.50438225_71141" />
+        <xref linkend="recover_ldiskfs_errors" />
       </para>
     </listitem>
     <listitem>
       <para>
-        <xref linkend="dbdoclet.50438225_37365" />
+        <xref linkend="recover_lustreFS_corruption" />
       </para>
     </listitem>
     <listitem>
       <para>
-        <xref linkend="dbdoclet.50438225_12316" />
+        <xref linkend="recover_unavailable_ost" />
       </para>
     </listitem>
     <listitem>
       <para>
-        <xref linkend="dbdoclet.lfsckadmin" />
+        <xref linkend="lfsckadmin" />
       </para>
     </listitem>
   </itemizedlist>
-  <section xml:id="dbdoclet.50438225_71141">
+  <section xml:id="recover_ldiskfs_errors">
     <title>
     <indexterm>
       <primary>recovery</primary>
@@ -93,7 +93,7 @@ root# e2fsck -fn /dev/sda   # don't fix file system, just check for corruption
 :
 root# e2fsck -fp /dev/sda   # fix errors with prudent answers (usually <literal>yes</literal>)</screen>
   </section>
-  <section xml:id="dbdoclet.50438225_37365">
+  <section xml:id="recover_lustreFS_corruption">
     <title>
     <indexterm>
       <primary>recovery</primary>
@@ -118,7 +118,7 @@ root# e2fsck -fp /dev/sda   # fix errors with prudent answers (usually <literal>
         necessary, to reduce the outage window.</para>
       </listitem>
     </orderedlist>
-    <section xml:id="dbdoclet.50438225_13916">
+    <section xml:id="orphan_objects">
       <title>
       <indexterm>
         <primary>recovery</primary>
@@ -135,7 +135,7 @@ root# e2fsck -fp /dev/sda   # fix errors with prudent answers (usually <literal>
        identify and process orphan objects found on MDTs as well.</para>
     </section>
   </section>
-  <section xml:id="dbdoclet.50438225_12316">
+  <section xml:id="recover_unavailable_ost">
     <title>
     <indexterm>
       <primary>recovery</primary>
@@ -181,7 +181,7 @@ root# e2fsck -fp /dev/sda   # fix errors with prudent answers (usually <literal>
       <xref linkend="lustrerecovery" />(Version-based Recovery).</para>
     </note>
   </section>
-  <section xml:id="dbdoclet.lfsckadmin">
+  <section xml:id="lfsckadmin">
     <title>
     <indexterm>
       <primary>recovery</primary>
@@ -205,7 +205,7 @@ root# e2fsck -fp /dev/sda   # fix errors with prudent answers (usually <literal>
       an internal table called the OI Table. An OI Scrub traverses the OI table
       and makes corrections where necessary. An OI Scrub is required after
       restoring from a file-level MDT backup (
-      <xref linkend="dbdoclet.backup_device" />), or in case the OI Table is
+      <xref linkend="backup_device" />), or in case the OI Table is
       otherwise corrupted. Later phases of LFSCK will add further checks to the
       Lustre distributed file system state. LFSCK namespace scanning can verify
       and repair the directory FID-in-dirent and LinkEA consistency.</para>
@@ -218,7 +218,7 @@ root# e2fsck -fp /dev/sda   # fix errors with prudent answers (usually <literal>
       is enhanced to support verify and repair inconsistencies between multiple
       MDTs.</para>
     <para>Control and monitoring of LFSCK is through LFSCK and the
-    <literal>/proc</literal> file system interfaces. LFSCK supports three types
+    <literal>lctl get_param</literal> command. LFSCK supports three types
     of interface: switch interface, status interface, and adjustment interface.
     These interfaces are detailed below.</para>
     <section>
@@ -822,7 +822,7 @@ root# e2fsck -fp /dev/sda   # fix errors with prudent answers (usually <literal>
           <title>Description</title>
           <para>The
           <literal>namespace</literal> component is responsible for checks
-          described in <xref linkend="dbdoclet.lfsckadmin" />. The
+          described in <xref linkend="lfsckadmin" />. The
           <literal>procfs</literal> interface for this component is in the
           MDD layer, named
           <literal>lfsck_namespace</literal>. To show the status of this
@@ -1482,7 +1482,7 @@ lctl set_param obdfilter.${FSNAME}-${OST_target}.lfsck_speed_limit=
           </informaltable>
         </section>
       </section>
-      <section xml:id="dbdoclet.lfsck_auto_scrub">
+      <section xml:id="lfsck_auto_scrub">
         <title>Auto scrub</title>
         <section>
           <title>Description</title>
@@ -1493,9 +1493,9 @@ lctl set_param obdfilter.${FSNAME}-${OST_target}.lfsck_speed_limit=
           below.</para>
           <para>There is also a
           <literal>noscrub</literal> mount option (see
-          <xref linkend="dbdoclet.50438219_12635" />) which can be used to
-          disable automatic OI scrub upon detection of a file-level backup at
-          mount time. If the
+          <xref linkend="mount.lustre" />) which
+          can be used to disable automatic OI scrub upon detection of a
+          file-level backup at mount time. If the
           <literal>noscrub</literal> mount option is specified,
           <literal>auto_scrub</literal> will also be disabled, so OI scrub will
           not be triggered when an OI inconsistency is detected. Auto scrub can
@@ -1544,3 +1544,6 @@ lctl set_param obdfilter.${FSNAME}-${OST_target}.lfsck_speed_limit=
     </section>
   </section>
 </chapter>
+<!--
+  vim:expandtab:shiftwidth=2:tabstop=8:
+  -->