Whamcloud - gitweb
LUDOC-126 startup: component start-up order.
authorRichard Henwood <richard.henwood@intel.com>
Fri, 8 Mar 2013 01:27:50 +0000 (19:27 -0600)
committerRichard Henwood <richard.henwood@intel.com>
Thu, 4 Apr 2013 20:47:37 +0000 (16:47 -0400)
Component startup order is now correct.

Signed-off-by: Richard Henwood <rhenwood@whamcloud.com>
Change-Id: I3b9f24323c539d042858e98a1566ce1fadee0748
Reviewed-on: http://review.whamcloud.com/5645
Tested-by: Hudson
Reviewed-by: Cliff White <cliff.white@intel.com>
Reviewed-by: Linda Bebernes <linda.bebernes@intel.com>
Reviewed-by: Cory Spitz <spitzcor@cray.com>
Reviewed-by: Richard Henwood <richard.henwood@intel.com>
LustreOperations.xml

index 0913a96..cf40c40 100644 (file)
@@ -64,18 +64,23 @@ Mounting by Label</title>
   </section>
   <section xml:id="dbdoclet.50438194_24122">
     <title><indexterm><primary>operations</primary><secondary>starting</secondary></indexterm>Starting Lustre</title>
-    <para>The startup order of Lustre components depends on whether you have a combined MGS/MDT or these components are separate.</para>
-    <itemizedlist>
+    <para>On the first start of a Lustre file system, the components must be started in the following order:</para>
+    <orderedlist>
       <listitem>
-        <para>If you have a combined MGS/MDT, the recommended startup order is OSTs, then the MGS/MDT, and then clients.</para>
+        <para>Mount the MGT.</para>
+               <note><para>If a combined MGT/MDT is present, Lustre will correctly mount the MGT and MDT automatically.</para></note>
       </listitem>
       <listitem>
-        <para> If the MGS and MDT are separate, the recommended startup order is: MGS, then OSTs, then the MDT, and then clients.</para>
+        <para>Mount the MDT.</para>
+               <note><para condition='l24'>Mount all MDTs if multiple MDTs are present.</para></note>
       </listitem>
-    </itemizedlist>
-    <note>
-      <para>If an OST is added to a Lustre file system with a combined MGS/MDT, then the startup order changes slightly; the MGS must be started first because the OST needs to write its configuration data to it. In this scenario, the startup order is MGS/MDT, then OSTs, then the clients.</para>
-    </note>
+      <listitem>
+        <para>Mount the OST(s).</para>
+      </listitem>
+      <listitem>
+        <para>Mount the client(s).</para>
+      </listitem>
+    </orderedlist>
   </section>
   <section xml:id="dbdoclet.50438194_84876">
     <title><indexterm><primary>operations</primary><secondary>mounting</secondary></indexterm>Mounting a Server</title>