LUDOC-14 Always use --index when formatting OSTs

To prepare users for changes that are upcoming in Lustre 2.3/2.4 for
the OSD restructuring project, the OST index should always be given
when formatting OSTs with mkfs.lustre.  This is already accepted as
standard practice for Lustre users today, so reflect that in the
examples in the manual.

Change-Id: I41cc175dc4392950c4376b3643c3017f6b9b2fcc
Signed-off-by: Andreas Dilger <adilger@whamcloud.com>

diff --git a/BackupAndRestore.xml b/BackupAndRestore.xml
index 315ae73..dd69a81 100644 (file)
--- a/BackupAndRestore.xml
+++ b/BackupAndRestore.xml
@@ -159,8 +159,8 @@
         <screen># lctl --device lustre-MDT0000 changelog_register lustre-MDT0000 Registered\
  changelog userid &apos;cl1&apos;</screen>
         <para>Synchronize a Lustre file system (<literal>/mnt/lustre</literal>) to a target file system (<literal>/mnt/target</literal>).</para>
-        <screen>$ lustre_rsync --source=/mnt/lustre --target=/mnt/target --mdt=lustre-MDT00\
-00 --user=cl1 --statuslog sync.log  --verbose 
+        <screen>$ lustre_rsync --source=/mnt/lustre --target=/mnt/target --mdt=lustre-MDT0000 \
+--user=cl1 --statuslog sync.log  --verbose 
 Lustre filesystem: lustre 
 MDT device: lustre-MDT0000 
 Source: /mnt/lustre 
@@ -332,15 +332,15 @@ cfs21:~# lvscan
         <listitem>
           <para>Format the LVM volumes as Lustre targets.</para>
           <para>In this example, the backup file system is called &apos;main&apos; and designates the current, most up-to-date backup.</para>
-          <screen>cfs21:~# mkfs.lustre --mdt --fsname=main /dev/volgroup/MDT
+          <screen>cfs21:~# mkfs.lustre --fsname=main --mdt --index=0 /dev/volgroup/MDT
  No management node specified, adding MGS to this MDT.
     Permanent disk data:
- Target:     main-MDTffff
- Index:      unassigned
+ Target:     main-MDT0000
+ Index:      0
  Lustre FS:  main
  Mount type: ldiskfs
  Flags:      0x75
-               (MDT MGS needs_index first_time update )
+               (MDT MGS first_time update )
  Persistent mount opts: errors=remount-ro,iopen_nopriv,user_xattr
  Parameters:
 checking for existing Lustre data
@@ -349,27 +349,28 @@ checking for existing Lustre data
          target name  main-MDTffff
          4k blocks     0
          options        -i 4096 -I 512 -q -O dir_index -F
- mkfs_cmd = mkfs.ext2 -j -b 4096 -L main-MDTffff  -i 4096 -I 512 -q -O dir_\
-index -F /dev/volgroup/MDT
+ mkfs_cmd = mkfs.ext2 -j -b 4096 -L main-MDTffff  -i 4096 -I 512 -q
+ -O dir_index -F /dev/volgroup/MDT
  Writing CONFIGS/mountdata
-cfs21:~# mkfs.lustre --ost --mgsnode=cfs21 --fsname=main /dev/volgroup/OST0
+cfs21:~# mkfs.lustre --mgsnode=cfs21 --fsname=main --ost --index=0 /dev/volgroup/OST0
     Permanent disk data:
- Target:     main-OSTffff
-Index:      unassigned
+ Target:     main-OST0000
+ Index:      0
  Lustre FS:  main
  Mount type: ldiskfs
  Flags:      0x72
-               (OST needs_index first_time update )
+               (OST first_time update )
  Persistent mount opts: errors=remount-ro,extents,mballoc
  Parameters: mgsnode=192.168.0.21@tcp
 checking for existing Lustre data
  device size = 200MB
  formatting backing filesystem ldiskfs on /dev/volgroup/OST0
-         target name  main-OSTffff
+         target name  main-OST0000
          4k blocks     0
          options        -I 256 -q -O dir_index -F
- mkfs_cmd = mkfs.ext2 -j -b 4096 -L main-OSTffff  -I 256 -q -O dir_index -F\
- /dev/ volgroup/OST0
+ mkfs_cmd = mkfs.ext2 -j -b 4096 -L lustre-OSTffff -J size=400 -I 256 
+  -i 262144 -O extents,uninit_bg,dir_nlink,huge_file,flex_bg -G 256 
+  -E resize=4290772992,lazy_journal_init, -F /dev/volgroup/OST0
  Writing CONFIGS/mountdata
 cfs21:~# mount -t lustre /dev/volgroup/MDT /mnt/mdt
 cfs21:~# mount -t lustre /dev/volgroup/OST0 /mnt/ost
@@ -411,8 +412,7 @@ fstab  passwd  termcap</screen>
         <listitem>
           <para>Rename the LVM snapshot.</para>
           <para>Rename the file system snapshot from &quot;main&quot; to &quot;back&quot; so you can mount it without unmounting &quot;main&quot;. This is recommended, but not required. Use the <literal>--reformat</literal> flag to <literal>tunefs.lustre</literal> to force the name change. For example:</para>
-          <screen>cfs21:~# tunefs.lustre --reformat --fsname=back --writeconf /dev/volgroup/M\
-DTb1
+          <screen>cfs21:~# tunefs.lustre --reformat --fsname=back --writeconf /dev/volgroup/MDTb1
  checking for existing Lustre data
  found Lustre data
  Reading CONFIGS/mountdata
@@ -435,8 +435,7 @@ Permanent disk data:
  Persistent mount opts: errors=remount-ro,iopen_nopriv,user_xattr
  Parameters:
 Writing CONFIGS/mountdata
-cfs21:~# tunefs.lustre --reformat --fsname=back --writeconf /dev/volgroup/O\
-STb1
+cfs21:~# tunefs.lustre --reformat --fsname=back --writeconf /dev/volgroup/OSTb1
  checking for existing Lustre data
  found Lustre data
  Reading CONFIGS/mountdata
@@ -459,8 +458,7 @@ Permanent disk data:
  Persistent mount opts: errors=remount-ro,extents,mballoc
  Parameters: mgsnode=192.168.0.21@tcp
 Writing CONFIGS/mountdata
-When renaming an FS, we must also erase the last_rcvd file from the snapsho\
-ts
+When renaming an FS, we must also erase the last_rcvd file from the snapshots
 cfs21:~# mount -t ldiskfs /dev/volgroup/MDTb1 /mnt/mdtback
 cfs21:~# rm /mnt/mdtback/last_rcvd
 cfs21:~# umount /mnt/mdtback
@@ -471,7 +469,7 @@ cfs21:~# umount /mnt/ostback</screen>
         <listitem>
           <para>Mount the file system from the LVM snapshot.</para>
           <para>For example:</para>
-          <screen>cfs21:~# mount -t lustre /dev/volgroup/MDTb1 /mnt/mdtback                  \
+          <screen>cfs21:~# mount -t lustre /dev/volgroup/MDTb1 /mnt/mdtback
                                                             
 cfs21:~# mount -t lustre /dev/volgroup/OSTb1 /mnt/ostback
 cfs21:~# mount -t lustre cfs21:/back /mnt/back</screen>

diff --git a/ConfiguringLustre.xml b/ConfiguringLustre.xml
index c1a0bcf..1d4c1cf 100644 (file)
--- a/ConfiguringLustre.xml
+++ b/ConfiguringLustre.xml
@@ -53,7 +53,7 @@
     <orderedlist>
       <listitem>
         <para>Create a combined MGS/MDT file system on a block device. On the MDS node, run:</para>
-        <screen>mkfs.lustre --fsname=&lt;<emphasis>fsname</emphasis>&gt; --mgs --mdt &lt;<emphasis>block device name</emphasis>&gt;</screen>
+        <screen>mkfs.lustre --fsname=&lt;<emphasis>fsname</emphasis>&gt; --mgs --mdt --index=0 &lt;<emphasis>block device name</emphasis>&gt;</screen>
         <para>The default file system name (<literal>fsname</literal>) is <literal>lustre</literal>.</para>
         <note>
           <para>If you plan to generate multiple file systems, the MGS should be created separately on its own dedicated block device, by running:</para>
@@ -69,13 +69,14 @@
       </listitem>
       <listitem xml:id="dbdoclet.50438267_pgfId-1290915">
         <para>Create the OST. On the OSS node, run:</para>
-        <screen>mkfs.lustre --ost --fsname=&lt;<emphasis>fsname</emphasis>&gt; --mgsnode=&lt;<emphasis>NID</emphasis>&gt; &lt;<emphasis>block device name</emphasis>&gt;</screen>
+        <screen>mkfs.lustre --fsname=&lt;<emphasis>fsname</emphasis>&gt; --mgsnode=&lt;<emphasis>NID</emphasis>&gt; --ost --index=&lt;<emphasis>OST index</emphasis>&gt; &lt;<emphasis>block device name</emphasis>&gt;</screen>
         <para>When you create an OST, you are formatting a <literal>ldiskfs</literal> file system on a block storage device like you would with any local file system.</para>
         <para>You can have as many OSTs per OSS as the hardware or drivers allow. For more information about storage and memory requirements for a Lustre file system, see <xref linkend="settinguplustresystem"/>.</para>
         <para>You can only configure one OST per block device. You should create an OST that uses the raw block device and does not use partitioning.</para>
+        <para>You should specify the OST index number at format time in order to simplify the translating the OST number in error messages or file striping to the OSS node and block device later on.</para>
         <para>If you are using block devices that are accessible from multiple OSS nodes, ensure that you mount the OSTs from only one OSS node at at time. It is strongly recommended that multiple-mount protection be enabled for such devices to prevent serious data corruption. For more information about multiple-mount protection, see <xref linkend="managingfailover"/>.</para>
         <note>
-          <para>Lustre currently supports block devices up to 16 TB on OEL 5/RHEL 5 (up to 8 TB on other distributions). If the device size is only slightly larger that 16 TB, it is recommended that you limit the file system size to 16 TB at format time. If the size is significantly larger than 16 TB, you should reconfigure the storage into devices smaller than 16 TB. We recommend that you not place partitions on top of RAID 5/6 block devices due to negative impacts on performance.</para>
+          <para>Lustre currently supports block devices up to 128 TB on RHEL 5/6 (up to 8 TB on other distributions). If the device size is only slightly larger that 16 TB, it is recommended that you limit the file system size to 16 TB at format time.  We recommend that you not place DOS partitions on top of RAID 5/6 block devices due to negative impacts on performance, but instead format the whole disk for the filesystem.</para>
         </note>
       </listitem>
       <listitem xml:id="dbdoclet.50438267_pgfId-1293955">
@@ -83,7 +84,7 @@
         <screen>mount -t lustre <emphasis>&lt;block device name&gt; &lt;mount point&gt;</emphasis></screen>
         <note>
           <para>
-              To create additional OSTs, repeat <xref linkend="dbdoclet.50438267_pgfId-1290915"/>Step 3 and <xref linkend="dbdoclet.50438267_pgfId-1293955"/>Step 4.</para>
+              To create additional OSTs, repeat <xref linkend="dbdoclet.50438267_pgfId-1290915"/>Step 3 and <xref linkend="dbdoclet.50438267_pgfId-1293955"/>Step 4, specifying the next higher OST index number.</para>
         </note>
       </listitem>
       <listitem xml:id="dbdoclet.50438267_pgfId-1290934">
@@ -411,15 +412,15 @@
       <orderedlist>
         <listitem>
           <para>Create a combined MGS/MDT file system on the block device. On the MDS node, run:</para>
-          <screen>[root@mds /]# mkfs.lustre --fsname=temp --mgs --mdt /dev/sdb</screen>
+          <screen>[root@mds /]# mkfs.lustre --fsname=temp --mgs --mdt --index=0 /dev/sdb</screen>
           <para>This command generates this output:</para>
           <screen>    Permanent disk data:
-Target:            temp-MDTffff
-Index:             unassigned
+Target:            temp-MDT0000
+Index:             0
 Lustre FS: temp
 Mount type:        ldiskfs
 Flags:             0x75
-   (MDT MGS needs_index first_time update )
+   (MDT MGS first_time update )
 Persistent mount opts: errors=remount-ro,iopen_nopriv,user_xattr
 Parameters: mdt.group_upcall=/usr/sbin/l_getgroups
  
@@ -450,15 +451,15 @@ Lustre: Server temp-MDT0000 on device /dev/sdb has started </screen>
           <orderedlist>
             <listitem>
               <para>Create <literal>ost1</literal>. On <literal>oss1</literal> node, run:</para>
-              <screen>[root@oss1 /]# mkfs.lustre --ost --fsname=temp --mgsnode=10.2.0.1@tcp0 /dev/sdc</screen>
+              <screen>[root@oss1 /]# mkfs.lustre --fsname=temp --mgsnode=10.2.0.1@tcp0 --ost --index=0 /dev/sdc</screen>
               <para>The command generates this output:</para>
               <screen>    Permanent disk data:
-Target:            temp-OSTffff
-Index:             unassigned
+Target:            temp-OST0000
+Index:             0
 Lustre FS: temp
 Mount type:        ldiskfs
 Flags:             0x72
-(OST needs_index first_time update)
+(OST first_time update)
 Persistent mount opts: errors=remount-ro,extents,mballoc
 Parameters: mgsnode=10.2.0.1@tcp
  
@@ -466,10 +467,10 @@ checking for existing Lustre data: not found
 device size = 16MB
 2 6 18
 formatting backing filesystem ldiskfs on /dev/sdc
-   target name             temp-OSTffff
+   target name             temp-OST0000
    4k blocks               0
    options                 -I 256 -q -O dir_index,uninit_groups -F
-mkfs_cmd = mkfs.ext2 -j -b 4096 -L temp-OSTffff  -I 256 -q -O
+mkfs_cmd = mkfs.ext2 -j -b 4096 -L temp-OST0000  -I 256 -q -O
 dir_index,uninit_groups -F /dev/sdc
 Writing CONFIGS/mountdata </screen>
             </listitem>
@@ -492,16 +493,16 @@ Lustre: MDS temp-MDT0000: temp-OST0000_UUID now active, resetting orphans </scre
           <orderedlist>
             <listitem>
               <para>Create ost2. On <literal>oss2</literal> node, run:</para>
-              <screen>[root@oss2 /]# mkfs.lustre --ost --fsname=temp --mgsnode=10.2.0.1@tcp0 /dev\
-/sdd</screen>
+              <screen>[root@oss2 /]# mkfs.lustre --fsname=temp --mgsnode=10.2.0.1@tcp0 \
+--ost --index=1 /dev/sdd</screen>
               <para>The command generates this output:</para>
               <screen>    Permanent disk data:
-Target:            temp-OSTffff
-Index:             unassigned
+Target:            temp-OST0001
+Index:             1
 Lustre FS: temp
 Mount type:        ldiskfs
 Flags:             0x72
-(OST needs_index first_time update)
+(OST first_time update)
 Persistent mount opts: errors=remount-ro,extents,mballoc
 Parameters: mgsnode=10.2.0.1@tcp
  
@@ -509,10 +510,10 @@ checking for existing Lustre data: not found
 device size = 16MB
 2 6 18
 formatting backing filesystem ldiskfs on /dev/sdd
-   target name             temp-OSTffff
+   target name             temp-OST0001
    4k blocks               0
    options                 -I 256 -q -O dir_index,uninit_groups -F
-mkfs_cmd = mkfs.ext2 -j -b 4096 -L temp-OSTffff  -I 256 -q -O
+mkfs_cmd = mkfs.ext2 -j -b 4096 -L temp-OST0001  -I 256 -q -O
 dir_index,uninit_groups -F /dev/sdc
 Writing CONFIGS/mountdata </screen>
             </listitem>
@@ -522,11 +523,11 @@ Writing CONFIGS/mountdata </screen>
               <para>The command generates this output:</para>
               <screen>LDISKFS-fs: file extents enabled 
 LDISKFS-fs: mballoc enabled
-Lustre: temp-OST0000: new disk, initializing
-Lustre: Server temp-OST0000 on device /dev/sdb has started</screen>
+Lustre: temp-OST0001: new disk, initializing
+Lustre: Server temp-OST0001 on device /dev/sdb has started</screen>
               <para>Shortly afterwards, this output appears:</para>
-              <screen>Lustre: temp-OST0000: received MDS connection from 10.2.0.1@tcp0
-Lustre: MDS temp-MDT0000: temp-OST0000_UUID now active, resetting orphans </screen>
+              <screen>Lustre: temp-OST0001: received MDS connection from 10.2.0.1@tcp0
+Lustre: MDS temp-MDT0000: temp-OST0001_UUID now active, resetting orphans </screen>
             </listitem>
           </orderedlist>
         </listitem>

diff --git a/ConfiguringStorage.xml b/ConfiguringStorage.xml
index e9f6b7b..1403936 100644 (file)
--- a/ConfiguringStorage.xml
+++ b/ConfiguringStorage.xml
@@ -126,9 +126,8 @@
         <listitem>
           <para>Create the OST.</para>
           <para>In this example, <literal>/dev/sdc</literal> is the RAID 6 device to be used as the OST, run:</para>
-          <screen>[oss#] mkfs.lustre --ost --mgsnode=mds@osib --mkfsoptions=&quot;-J device=/dev/sd\
-b1&quot; /dev/sdc
-</screen>
+          <screen>[oss#] mkfs.lustre --mgsnode=mds@osib --ost --index=0 \
+--mkfsoptions=&quot;-J device=/dev/sdb1&quot; /dev/sdc</screen>
         </listitem>
         <listitem>
           <para>Mount the OST as usual.</para>

diff --git a/LustreMaintenance.xml b/LustreMaintenance.xml
index d787644..82d4889 100644 (file)
--- a/LustreMaintenance.xml
+++ b/LustreMaintenance.xml
@@ -266,9 +266,9 @@ Adding a New OST to a Lustre File System</title>
       <orderedlist>
         <listitem>
           <para> Add a new OST by passing on the following commands, run:</para>
-          <screen>$ mkfs.lustre --fsname=spfs --ost --mgsnode=mds16@tcp0 /dev/sda
-$ mkdir -p /mnt/test/ost0
-$ mount -t lustre /dev/sda /mnt/test/ost0                 </screen>
+          <screen>$ mkfs.lustre --fsname=spfs --mgsnode=mds16@tcp0 --ost --index=12 /dev/sda
+$ mkdir -p /mnt/test/ost12
+$ mount -t lustre /dev/sda /mnt/test/ost12</screen>
         </listitem>
         <listitem>
           <para> Migrate the data (possibly).</para>

diff --git a/LustreOperations.xml b/LustreOperations.xml
index 586c0c3..504a676 100644 (file)
--- a/LustreOperations.xml
+++ b/LustreOperations.xml
@@ -86,7 +86,7 @@ Mounting by Label</title>
     <screen>LABEL=testfs-MDT0000 /mnt/test/mdt lustre defaults,_netdev,noauto 0 0
 LABEL=testfs-OST0000 /mnt/test/ost0 lustre defaults,_netdev,noauto 0 0</screen>
     <para>In general, it is wise to specify noauto and let your high-availability (HA) package manage when to mount the device. If you are not using failover, make sure that networking has been started before mounting a Lustre server. RedHat, SuSE, Debian (and perhaps others) use the <literal>_netdev</literal> flag to ensure that these disks are mounted after the network is up.</para>
-    <para>We are mounting by disk label here--the label of a device can be read with <literal>e2label</literal>. The label of a newly-formatted Lustre server ends in <literal>FFFF</literal>, meaning that it has yet to be assigned. The assignment takes place when the server is first started, and the disk label is updated.</para>
+    <para>We are mounting by disk label here. The label of a device can be read with <literal>e2label</literal>. The label of a newly-formatted Lustre server may end in <literal>FFFF</literal> if the <literal>--index</literal> option is not specified to <literal>mkfs.lustre</literal>, meaning that it has yet to be assigned. The assignment takes place when the server is first started, and the disk label is updated.  It is recommended that the <literal>--index</literal> option always be used, which will also ensure that the label is set at format time.</para>
     <caution>
       <para>Do not do this when the client and OSS are on the same node, as memory pressure between the client and OSS can lead to deadlocks.</para>
     </caution>
@@ -117,9 +117,9 @@ LABEL=testfs-OST0000 /mnt/test/ost0 lustre defaults,_netdev,noauto 0 0</screen>
       </listitem>
     </itemizedlist>
     <para>By default, the Lustre file system uses failover mode for OSTs. To specify failout mode instead, run this command:</para>
-    <screen>$ mkfs.lustre --fsname=&lt;fsname&gt; --ost --mgsnode=&lt;MGS node NID&gt; --param=&quot;failover.mode=failout&quot; &lt;block device name&gt;</screen>
+    <screen>$ mkfs.lustre --fsname=&lt;fsname&gt; --mgsnode=&lt;MGS node NID&gt; --param=&quot;failover.mode=failout&quot; --ost --index=&quot;OST index&quot; &lt;block device name&gt;</screen>
     <para>In this example, failout mode is specified for the OSTs on MGS <literal>uml1</literal>, file system <literal>testfs</literal>.</para>
-    <screen>$ mkfs.lustre --fsname=testfs --ost --mgsnode=uml1 --param=&quot;failover.mode=failout&quot; /dev/sdb </screen>
+    <screen>$ mkfs.lustre --fsname=testfs --mgsnode=uml1 --param=&quot;failover.mode=failout&quot; --ost --index=3 /dev/sdb </screen>
     <caution>
       <para>Before running this command, unmount all OSTs that will be affected by the change in the failover/failout mode.</para>
     </caution>
@@ -146,15 +146,15 @@ LABEL=testfs-OST0000 /mnt/test/ost0 lustre defaults,_netdev,noauto 0 0</screen>
   <section xml:id="dbdoclet.50438194_88063">
     <title><indexterm><primary>operations</primary><secondary>multiple file systems</secondary></indexterm>Running Multiple Lustre File Systems</title>
     <para>There may be situations in which you want to run multiple file systems. This is doable, as long as you follow specific naming conventions.</para>
-    <para>By default, the <literal>mkfs.lustre</literal> command creates a file system named <literal>lustre</literal>. To specify a different file system name (limited to 8 characters), run this command:</para>
-    <para><screen>mkfs.lustre --fsname=&lt;new file system name&gt;</screen></para>
+    <para>By default, the <literal>mkfs.lustre</literal> command creates a file system named <literal>lustre</literal>. To specify a different file system name (limited to 8 characters) at format time, use the <literal>--fsname</literal> option:</para>
+    <para><screen>mkfs.lustre --fsname=&lt;file system name&gt;</screen></para>
     <note>
-      <para>The MDT, OSTs and clients in the new file system must share the same name (prepended to the device name). For example, for a new file system named <literal>foo</literal>, the MDT and two OSTs would be named <literal>foo-MDT0000</literal>, <literal>foo-OST0000</literal>, and <literal>foo-OST0001</literal>.</para>
+      <para>The MDT, OSTs and clients in the new file system must use the same filesystem name (prepended to the device name). For example, for a new file system named <literal>foo</literal>, the MDT and two OSTs would be named <literal>foo-MDT0000</literal>, <literal>foo-OST0000</literal>, and <literal>foo-OST0001</literal>.</para>
     </note>
     <para>To mount a client on the file system, run:</para>
     <screen>mount -t lustre mgsnode:/&lt;new fsname&gt; &lt;mountpoint&gt;</screen>
-    <para>For example, to mount a client on file system foo at mount point /mnt/lustre1, run:</para>
-    <screen>mount -t lustre mgsnode:/foo /mnt/lustre1</screen>
+    <para>For example, to mount a client on file system foo at mount point /mnt/foo, run:</para>
+    <screen>mount -t lustre mgsnode:/foo /mnt/foo</screen>
     <note>
       <para>If a client(s) will be mounted on several file systems, add the following line to <literal>/etc/xattr.conf</literal> file to avoid problems when files are moved between the file systems: <literal>lustre.* skip</literal></para>
     </note>
@@ -162,26 +162,20 @@ LABEL=testfs-OST0000 /mnt/test/ost0 lustre defaults,_netdev,noauto 0 0</screen>
       <para>The MGS is universal; there is only one MGS per Lustre installation, not per file system.</para>
     </note>
     <note>
-      <para>There is only one file system per MDT. Therefore, specify <literal>--mdt --mgs</literal> on one file system and -<literal>-mdt --mgsnode=&lt;MGS node NID&gt;</literal> on the other file systems.</para>
+      <para>There is only one file system per MDT. Therefore, specify <literal>--mdt --mgs</literal> on one file system and <literal>--mdt --mgsnode=&lt;MGS node NID&gt;</literal> on the other file systems.</para>
     </note>
-    <para>A Lustre installation with two file systems (<literal>foo</literal> and <literal>bar</literal>) could look like this, where the MGS node is <literal>mgsnode@tcp0</literal> and the mount points are <literal>/mnt/lustre1</literal> and <literal>/mnt/lustre2</literal>.</para>
-    <screen>mgsnode# mkfs.lustre --mgs /mnt/lustre1
-mdtfoonode# mkfs.lustre --fsname=foo --mdt --mgsnode=mgsnode@tcp0 /mnt/lust\
-re1
-ossfoonode# mkfs.lustre --fsname=foo --ost --mgsnode=mgsnode@tcp0 /mnt/lust\
-re1
-ossfoonode# mkfs.lustre --fsname=foo --ost --mgsnode=mgsnode@tcp0 /mnt/lust\
-re2
-mdtbarnode# mkfs.lustre --fsname=bar --mdt --mgsnode=mgsnode@tcp0 /mnt/lust\
-re1
-ossbarnode# mkfs.lustre --fsname=bar --ost --mgsnode=mgsnode@tcp0 /mnt/lust\
-re1
-ossbarnode# mkfs.lustre --fsname=bar --ost --mgsnode=mgsnode@tcp0 /mnt/lust\
-re2</screen>
-    <para>To mount a client on file system foo at mount point <literal>/mnt/lustre1</literal>, run:</para>
-    <screen>mount -t lustre mgsnode@tcp0:/foo /mnt/lustre1</screen>
-    <para>To mount a client on file system bar at mount point <literal>/mnt/lustre2</literal>, run:</para>
-    <screen>mount -t lustre mgsnode@tcp0:/bar /mnt/lustre2</screen>
+    <para>A Lustre installation with two file systems (<literal>foo</literal> and <literal>bar</literal>) could look like this, where the MGS node is <literal>mgsnode@tcp0</literal> and the mount points are <literal>/mnt/foo</literal> and <literal>/mnt/bar</literal>.</para>
+    <screen>mgsnode# mkfs.lustre --mgs /dev/sda
+mdtfoonode# mkfs.lustre --fsname=foo --mgsnode=mgsnode@tcp0 --mdt --index=0 /dev/sdb
+ossfoonode# mkfs.lustre --fsname=foo --mgsnode=mgsnode@tcp0 --ost --index=0 /dev/sda
+ossfoonode# mkfs.lustre --fsname=foo --mgsnode=mgsnode@tcp0 --ost --index=1 /dev/sdb
+mdtbarnode# mkfs.lustre --fsname=bar --mgsnode=mgsnode@tcp0 --mdt --index=0 /dev/sda
+ossbarnode# mkfs.lustre --fsname=bar --mgsnode=mgsnode@tcp0 --ost --index=0 /dev/sdc
+ossbarnode# mkfs.lustre --fsname=bar --mgsnode=mgsnode@tcp0 --ost --index=1 /dev/sdd</screen>
+    <para>To mount a client on file system foo at mount point <literal>/mnt/foo</literal>, run:</para>
+    <screen>mount -t lustre mgsnode@tcp0:/foo /mnt/foo</screen>
+    <para>To mount a client on file system bar at mount point <literal>/mnt/bar</literal>, run:</para>
+    <screen>mount -t lustre mgsnode@tcp0:/bar /mnt/bar</screen>
   </section>
   <section xml:id="dbdoclet.50438194_88980">
     <title><indexterm><primary>operations</primary><secondary>parameters</secondary></indexterm>Setting and Retrieving Lustre Parameters</title>
@@ -281,10 +275,10 @@ osc.myth-OST0004-osc-ffff88006dd20000.filesfree=129651</screen>
     <screen>lctl list_nids</screen>
     <para>This displays the server&apos;s NIDs (networks configured to work with Lustre).</para>
     <para>This example has a combined MGS/MDT failover pair on uml1 and uml2, and a OST failover pair on uml3 and uml4. There are corresponding Elan addresses on uml1 and uml2.</para>
-    <screen>uml1&gt; mkfs.lustre --fsname=testfs --mdt --mgs --failnode=uml2,2@elan /dev/sda1
+    <screen>uml1&gt; mkfs.lustre --fsname=testfs --mgs --mdt --index=0 --failnode=uml2,2@elan /dev/sda1
 uml1&gt; mount -t lustre /dev/sda1 /mnt/test/mdt
-uml3&gt; mkfs.lustre --fsname=testfs --ost --failnode=uml4 --mgsnode=uml1,1@ela\
-n --mgsnode=uml2,2@elan /dev/sdb
+uml3&gt; mkfs.lustre --fsname=testfs --failnode=uml4 --mgsnode=uml1,1@elan \
+--mgsnode=uml2,2@elan --ost --index=0 /dev/sdb
 uml3&gt; mount -t lustre /dev/sdb /mnt/test/ost0
 client&gt; mount -t lustre uml1,1@elan:uml2,2@elan:/testfs /mnt/testfs
 uml1&gt; umount /mnt/mdt
@@ -296,8 +290,8 @@ uml2&gt; cat /proc/fs/lustre/mds/testfs-MDT0000/recovery_status</screen>
       <orderedlist>
         <listitem>
           <para>On the OST, list the NIDs of all MGS nodes at <literal>mkfs</literal> time.</para>
-          <screen>OST# mkfs.lustre --fsname sunfs --ost --mgsnode=10.0.0.1 \
-  --mgsnode=10.0.0.2 /dev/{device}</screen>
+          <screen>OST# mkfs.lustre --fsname sunfs --mgsnode=10.0.0.1 \
+  --mgsnode=10.0.0.2 --ost --index=0 /dev/sdb</screen>
         </listitem>
         <listitem>
           <para>On the client, mount the file system.</para>
@@ -319,11 +313,11 @@ uml2&gt; cat /proc/fs/lustre/mds/testfs-MDT0000/recovery_status</screen>
       </listitem>
       <listitem>
         <para>Erase the file system and, presumably, replace it with another file system, run:</para>
-        <screen>$ mkfs.lustre -reformat --fsname spfs --mdt --mgs /dev/sda</screen>
+        <screen>$ mkfs.lustre --reformat --fsname spfs --mgs --mdt --index=0 /dev/sda</screen>
       </listitem>
       <listitem>
         <para>If you have a separate MGS (that you do not want to reformat), then add the &quot;writeconf&quot; flag to <literal>mkfs.lustre</literal> on the MDT, run:</para>
-        <screen>$ mkfs.lustre --reformat --writeconf -fsname spfs --mdt \ --mgs /dev/sda</screen>
+        <screen>$ mkfs.lustre --reformat --writeconf -fsname spfs --mgs --mdt --index=0 /dev/sda</screen>
       </listitem>
     </orderedlist>
     <note>

diff --git a/ManagingFileSystemIO.xml b/ManagingFileSystemIO.xml
index 05b2e21..55b01ec 100644 (file)
--- a/ManagingFileSystemIO.xml
+++ b/ManagingFileSystemIO.xml
@@ -297,9 +297,9 @@ filesystem summary:  11.8G 7.3G            3.9G    61%                     \
     <orderedlist>
       <listitem>
         <para>Add a new OST by passing on the following commands, run:</para>
-        <screen>$ mkfs.lustre --fsname=spfs --ost --mgsnode=mds16@tcp0 /dev/sda
-$ mkdir -p /mnt/test/ost0
-$ mount -t lustre /dev/sda /mnt/test/ost0</screen>
+        <screen>$ mkfs.lustre --fsname=spfs --mgsnode=mds16@tcp0 --ost --index=12 /dev/sda
+$ mkdir -p /mnt/test/ost12
+$ mount -t lustre /dev/sda /mnt/test/ost12</screen>
       </listitem>
       <listitem>
         <para>Migrate the data (possibly).</para>

diff --git a/ManagingLNET.xml b/ManagingLNET.xml
index 4defefa..c754977 100644 (file)
--- a/ManagingLNET.xml
+++ b/ManagingLNET.xml
@@ -154,10 +154,10 @@ $ mkfs.lustre --fsname lustre --mdt --mgs /dev/sda
 $ mkdir -p /mnt/test/mdt
 $ mount -t lustre /dev/sda /mnt/test/mdt   
 $ mount -t lustre mgs@o2ib0:/lustre /mnt/mdt
-$ mkfs.lustre --fsname lustre --ost --mgsnode=mds@o2ib0 /dev/sda
+$ mkfs.lustre --fsname lustre --mgsnode=mds@o2ib0 --ost --index=0 /dev/sda
 $ mkdir -p /mnt/test/mdt
 $ mount -t lustre /dev/sda /mnt/test/ost   
-$ mount -t lustre mgs@o2ib0:/lustre /mnt/ost</screen>
+$ mount -t lustre mgs@o2ib0:/lustre /mnt/ost0</screen>
         </listitem>
         <listitem>
           <para>Mount the clients.</para>

diff --git a/SystemConfigurationUtilities.xml b/SystemConfigurationUtilities.xml
index 7d30c8d..5d40c5e 100644 (file)
--- a/SystemConfigurationUtilities.xml
+++ b/SystemConfigurationUtilities.xml
@@ -1592,7 +1592,7 @@ mkfs.lustre</title>
                 <para> <emphasis role="bold">--index</emphasis>=<emphasis>index</emphasis></para>
               </entry>
               <entry>
-                <para>  Forces a particular OST or MDT index.</para>
+                <para>  Specifies the OST or MDT number.  This should always be used when formatting OSTs, in order to ensure that there is a simple mapping between the OST index and the OSS node and device it is located on.</para>
               </entry>
             </row>
             <row>
@@ -1611,7 +1611,7 @@ mkfs.lustre</title>
                 <para>  Sets the mount options used when the backing file system is mounted.</para>
                 <para><emphasis role="bold">CAUTION</emphasis>: Unlike earlier versions of mkfs.lustre, this version completely replaces the default mount options with those specified on the command line, and issues a warning on stderr if any default mount options are omitted.</para>
                 <para>The defaults for ldiskfs are:</para>
-                <para>OST: <emphasis>errors=remount-ro,mballoc,extents</emphasis>;</para>
+                <para>OST: <emphasis>errors=remount-ro</emphasis>;</para>
                 <para>MGS/MDT: <emphasis>errors=remount-ro,iopen_nopriv,user_xattr</emphasis></para>
                 <para>Do not alter the default mount options unless you know what you are doing.</para>
               </entry>
@@ -1726,7 +1726,7 @@ mkfs.lustre</title>
       <para>Creates a combined MGS and MDT for file system <emphasis role="bold">testfs</emphasis> on, e.g., node <emphasis role="bold">cfs21</emphasis>:</para>
       <screen>mkfs.lustre --fsname=testfs --mdt --mgs /dev/sda1</screen>
       <para>Creates an OST for file system <emphasis role="bold">testfs</emphasis> on any node (using the above MGS):</para>
-      <screen>mkfs.lustre --fsname=testfs --ost --mgsnode=cfs21@tcp0 /dev/sdb</screen>
+      <screen>mkfs.lustre --fsname=testfs --mgsnode=cfs21@tcp0 --ost --index=0 /dev/sdb</screen>
       <para>Creates a standalone MGS on, e.g., node <emphasis role="bold">cfs22</emphasis>:</para>
       <screen>mkfs.lustre --mgs /dev/sda1</screen>
       <para>Creates an MDT for file system <emphasis role="bold">myfs1</emphasis> on any node (using the above MGS):</para>