FIX: validation, ulink -> link

diff --git a/LustreTroubleshooting.xml b/LustreTroubleshooting.xml
index daf71da..81c34d9 100644 (file)
--- a/LustreTroubleshooting.xml
+++ b/LustreTroubleshooting.xml
@@ -46,7 +46,7 @@
               </entry>
               <entry>
                 <literal>
-                  <para> -EPERM</para>
+                   -EPERM
                 </literal>
               </entry>
               <entry>
@@ -55,11 +55,11 @@
             </row>
             <row>
               <entry>
-                <para> -2</para>
+                 -2
               </entry>
               <entry>
                 <literal>
-                  <para> -ENOENT</para>
+                   -ENOENT
                 </literal>
               </entry>
               <entry>
@@ -72,7 +72,7 @@
               </entry>
               <entry>
                 <literal>
-                  <para> -EINTR</para>
+                   -EINTR
                 </literal>
               </entry>
               <entry>
@@ -85,7 +85,7 @@
               </entry>
               <entry>
                 <literal>
-                  <para> -EIO</para>
+                   -EIO
                 </literal>
               </entry>
               <entry>
@@ -98,7 +98,7 @@
               </entry>
               <entry>
                 <literal>
-                  <para> -ENODEV</para>
+                   -ENODEV
                 </literal>
               </entry>
               <entry>
@@ -111,7 +111,7 @@
               </entry>
               <entry>
                 <literal>
-                  <para> -EINVAL</para>
+                   -EINVAL
                 </literal>
               </entry>
               <entry>
@@ -124,7 +124,7 @@
               </entry>
               <entry>
                 <literal>
-                  <para> -ENOSPC</para>
+                   -ENOSPC
                 </literal>
               </entry>
               <entry>
@@ -137,7 +137,7 @@
               </entry>
               <entry>
                 <literal>
-                  <para> -EROFS</para>
+                   -EROFS
                 </literal>
               </entry>
               <entry>
@@ -150,7 +150,7 @@
               </entry>
               <entry>
                 <literal>
-                  <para> -EIDRM</para>
+                   -EIDRM
                 </literal>
               </entry>
               <entry>
@@ -163,7 +163,7 @@
               </entry>
               <entry>
                 <literal>
-                  <para> -ENOTCONN</para>
+                   -ENOTCONN
                 </literal>
               </entry>
               <entry>
@@ -176,7 +176,7 @@
               </entry>
               <entry>
                 <literal>
-                  <para> -ETIMEDOUT</para>
+                   -ETIMEDOUT
                 </literal>
               </entry>
               <entry>
@@ -273,11 +273,11 @@
           <screen>$ lctl --device &lt;OST device name or number&gt; deactivate</screen>
           <para>The OST device number or device name is generated by the lctl dl command.</para>
           <para>The <literal>deactivate</literal> command prevents clients from creating new objects on the specified OST, although you can still access the OST for reading.</para>
-        </listitem>
         <note>
           <para>If the OST later becomes available it needs to be reactivated, run:</para>
           <screen># lctl --device &lt;OST device name or number&gt; activate</screen>
         </note>
+        </listitem>
         <listitem>
           <para>Determine all files that are striped over the missing OST, run:</para>
           <screen># lfs getstripe -r -O {OST_UUID} /mountpoint</screen>
@@ -290,11 +290,11 @@
         <listitem>
           <para>You can delete these files with the unlink or munlink command.</para>
           <screen># unlink|munlink filename {filename ...} </screen>
-        </listitem>
         <note>
           <para>There is no functional difference between the <literal>unlink</literal> and <literal>munlink</literal> commands. The unlink command is for newer Linux distributions. You can run <literal>munlink</literal> if <literal>unlink</literal> is not available.</para>
           <para>When you run the <literal>unlink</literal> or <literal>munlink</literal> command, the file on the MDS is permanently removed.</para>
         </note>
+        </listitem>
         <listitem>
           <para>If you need to know, specifically, which parts of the file are missing data, then you first need to determine the file layout (striping pattern), which includes the index of the missing OST). Run:</para>
           <screen># lfs getstripe -v {filename}</screen>
@@ -447,7 +447,7 @@ tail -30 /tmp/objects.{diskname}</screen>
       <para>A Linux error -28 (<literal>ENOSPC</literal>) that occurs when a new file is being created may indicate that the MDS has run out of inodes and needs to be made larger. Newly created files do not written to full OSTs, while existing files continue to reside on the OST where they were initially created. To view inode information on the MDS, enter:</para>
       <screen>lfs df -i</screen>
       <para>Typically, Lustre reports this error to your application. If the application is checking the return code from its function calls, then it decodes it into a textual error message such as <literal>No space left on device</literal>. Both versions of the error message also appear in the system log.</para>
-      <para>For more information about the <literal>lfs df</literal> command, see <xref linkend="dbdoclet.50438209_35838">Checking File System Free Space</xref>.</para>
+      <para>For more information about the <literal>lfs df</literal> command, see <xref linkend="dbdoclet.50438209_35838"/>.</para>
       <para>Although it is less efficient, you can also use the grep command to determine which OST or MDS is running out of space. To check the free space and inodes on a client, enter:</para>
       <screen>grep &apos;[0-9]&apos; /proc/fs/lustre/osc/*/kbytes{free,avail,total}
 grep &apos;[0-9]&apos; /proc/fs/lustre/osc/*/files{free,total}
@@ -544,7 +544,7 @@ ptlrpc_main+0x42e/0x7c0 [ptlrpc]
           <para> Lustre or kernel stack traces showing processes stuck in &quot;<literal>try_to_free_pages</literal>&quot;</para>
         </listitem>
       </itemizedlist>
-      <para>For information on determining the MDS memory and OSS memory requirements, see <xref linkend="dbdoclet.50438256_26456">Determining Memory Requirements</xref>.</para>
+      <para>For information on determining the MDS memory and OSS memory requirements, see <xref linkend="dbdoclet.50438256_26456"/>.</para>
     </section>
     <section remap="h3">
       <title>26.3.14 Setting SCSI I/O Sizes</title>

diff --git a/LustreTuning.xml b/LustreTuning.xml
index eb2f777..4bb3a2b 100644 (file)
--- a/LustreTuning.xml
+++ b/LustreTuning.xml
@@ -61,7 +61,7 @@
       <screen>options ost oss_num_threads={N}</screen>
       <para>After startup, the minimum and maximum number of OSS thread counts can be set via the <literal>{service}.thread_{min,max,started}</literal> tunable. To change the tunable at runtime, run:</para>
       <para><screen>lctl {get,set}_param {service}.thread_{min,max,started}</screen></para>
-      <para>For details, see <xref linkend="dbdoclet.50438271_87260">Setting MDS and OSS Thread Counts</xref>.</para>
+      <para>For details, see <xref linkend="dbdoclet.50438271_87260"/>.</para>
     </section>
     <section remap="h3">
       <title>25.1.2 Specifying the MDS Service Thread Count</title>
@@ -69,7 +69,7 @@
       <screen>options mds mds_num_threads={N}</screen>
       <para>After startup, the minimum and maximum number of MDS thread counts can be set via the <literal>{service}.thread_{min,max,started}</literal> tunable. To change the tunable at runtime, run:</para>
       <para><screen>lctl {get,set}_param {service}.thread_{min,max,started}</screen></para>
-      <para>For details, see <xref linkend="dbdoclet.50438271_87260">Setting MDS and OSS Thread Counts</xref>.</para>
+      <para>For details, see <xref linkend="dbdoclet.50438271_87260"/>.</para>
       <para>At this time, no testing has been done to determine the optimal number of MDS threads. The default value varies, based on server size, up to a maximum of 32. The maximum number of threads (<literal>MDS_MAX_THREADS</literal>) is 512.</para>
       <note>
         <para>The OSS and MDS automatically start new service threads dynamically, in response to server load within a factor of 4. The default value is calculated the same way as before. Setting the <literal>_mu_threads</literal> module parameter disables automatic thread creation behavior.</para>

diff --git a/TroubleShootingRecovery.xml b/TroubleShootingRecovery.xml
index d02d255..173a757 100644 (file)
--- a/TroubleShootingRecovery.xml
+++ b/TroubleShootingRecovery.xml
@@ -16,6 +16,7 @@
       <para><xref linkend="dbdoclet.50438225_12316"/></para>
     </listitem>
   </itemizedlist>
+
   <section xml:id="dbdoclet.50438225_71141">
     <title>27.1 Recovering from Errors or Corruption on a Backing File System</title>
     <para>When an OSS, MDS, or MGS server crash occurs, it is not necessary to run e2fsck on the file system. <literal>ldiskfs</literal> journaling ensures that the file system remains coherent. The backing file systems are never accessed directly from the client, so client crashes are not relevant.</para>