LUDOC-382 Tag lfsck_query as lustre 2.9

[doc/manual.git] / LustreOperations.xml

diff --git a/LustreOperations.xml b/LustreOperations.xml
index 18acb13..51daff3 100644 (file)
--- a/LustreOperations.xml
+++ b/LustreOperations.xml
@@ -292,7 +292,7 @@ $ tunefs.lustre --param failover.mode=failout
       </para>
     </note>
   </section>
-  <section xml:id="dbdoclet.50438194_54138">
+  <section xml:id="dbdoclet.degraded_ost">
     <title>
     <indexterm>
       <primary>operations</primary>
@@ -324,7 +324,9 @@ lctl get_param obdfilter.*.degraded
     resets to 
     <literal>0</literal>.</para>
     <para>It is recommended that this be implemented by an automated script
-    that monitors the status of individual RAID devices.</para>
+    that monitors the status of individual RAID devices, such as MD-RAID's
+    <literal>mdadm(8)</literal> command with the <literal>--monitor</literal>
+    option to mark an affected device degraded or restored.</para>
   </section>
   <section xml:id="dbdoclet.50438194_88063">
     <title>
@@ -497,7 +499,7 @@ client# lfs mkdir –i
     <para>The Lustre 2.8 DNE feature enables individual files in a given
     directory to store their metadata on separate MDTs (a <emphasis>striped
     directory</emphasis>) once additional MDTs have been added to the
-    filesystem, see <xref linkend="dbdoclet.addingamdt"/>.
+    filesystem, see <xref linkend="dbdoclet.adding_new_mdt"/>.
     The result of this is that metadata requests for
     files in a striped directory are serviced by multiple MDTs and metadata
     service load is distributed over all the MDTs that service a given
@@ -577,8 +579,8 @@ mds# tunefs.lustre --erase-params --param=
 <replaceable>new_parameters</replaceable> 
 </screen>
       <para>The tunefs.lustre command can be used to set any parameter settable
-      in a /proc/fs/lustre file and that has its own OBD device, so it can be
-      specified as 
+      via <literal>lctl conf_param</literal> and that has its own OBD device,
+      so it can be specified as 
       <literal>
       <replaceable>obdname|fsname</replaceable>.
       <replaceable>obdtype</replaceable>.
@@ -600,8 +602,8 @@ mds# tunefs.lustre --param mdt.identity_upcall=NONE /dev/sda1
       are active as long as the server or client is not shut down. Permanent
       parameters live through server and client reboots.</para>
       <note>
-        <para>The lctl list_param command enables users to list all parameters
-        that can be set. See 
+        <para>The <literal>lctl list_param</literal> command enables users to
+          list all parameters that can be set. See 
         <xref linkend="dbdoclet.50438194_88217" />.</para>
       </note>
       <para>For more details about the 
@@ -616,7 +618,7 @@ mds# tunefs.lustre --param mdt.identity_upcall=NONE /dev/sda1
         <literal>/proc/{fs,sys}/{lnet,lustre}</literal>. The 
         <literal>lctl set_param</literal> command uses this syntax:</para>
         <screen>
-lctl set_param [-n] 
+lctl set_param [-n] [-P]
 <replaceable>obdtype</replaceable>.
 <replaceable>obdname</replaceable>.
 <replaceable>proc_file_name</replaceable>=
@@ -634,7 +636,7 @@ osc.myth-OST0004-osc.max_dirty_mb=32
       </section>
       <section xml:id="dbdoclet.50438194_64195">
         <title>Setting Permanent Parameters</title>
-        <para>Use the 
+        <para>Use <literal>lctl set_param -P</literal> or
         <literal>lctl conf_param</literal> command to set permanent parameters.
         In general, the 
         <literal>lctl conf_param</literal> command can be used to specify any
@@ -669,13 +671,12 @@ $ lctl conf_param testfs.sys.timeout=40
       </section>
       <section xml:id="dbdoclet.setparamp" condition='l25'>
         <title>Setting Permanent Parameters with lctl set_param -P</title>
-        <para>Use the 
-        <literal>lctl set_param -P</literal> to set parameters permanently. This
-        command must be issued on the MGS. The given parameter is set on every
-        host using 
-        <literal>lctl</literal> upcall. Parameters map to items in 
-        <literal>/proc/{fs,sys}/{lnet,lustre}</literal>. The 
-        <literal>lctl set_param</literal> command uses this syntax:</para>
+        <para>The <literal>lctl set_param -P</literal> command can also
+          set parameters permanently. This command must be issued on the MGS.
+          The given parameter is set on every host using 
+          <literal>lctl</literal> upcall. Parameters map to items in 
+          <literal>/proc/{fs,sys}/{lnet,lustre}</literal>. The 
+          <literal>lctl set_param</literal> command uses this syntax:</para>
         <screen>
 lctl set_param -P 
 <replaceable>obdtype</replaceable>.
@@ -921,7 +922,7 @@ tune2fs [-m reserved_blocks_percent] /dev/
     <para>To copy the contents of an existing OST to a new OST (or an old MDT
     to a new MDT), follow the process for either OST/MDT backups in 
     <xref linkend='dbdoclet.backup_device' />or 
-    <xref linkend='dbdoclet.backup_target_filesystem' />.
+    <xref linkend='backup_fs_level' />.
     For more information on removing a MDT, see 
     <xref linkend='dbdoclet.rmremotedir' />.</para>
   </section>