Whamcloud - gitweb
LUDOC-232 lfsck: remove mention of old lfsck
[doc/manual.git] / UserUtilities.xml
index cfad87e..3f6d562 100644 (file)
@@ -1,5 +1,4 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!-- This document was created with Syntext Serna Free. --><chapter xmlns="http://docbook.org/ns/docbook" xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en-US" xml:id="userutilities">
+<?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="userutilities">
   <title xml:id="userutilities.title">User Utilities</title>
   <para>This chapter describes user utilities and includes the following sections:</para>
   <itemizedlist>
@@ -10,9 +9,6 @@
       <para><xref linkend="dbdoclet.50438206_42260"/></para>
     </listitem>
     <listitem>
-      <para><xref linkend="dbdoclet.50438206_91700"/></para>
-    </listitem>
-    <listitem>
       <para><xref linkend="dbdoclet.50438206_75125"/></para>
     </listitem>
     <listitem>
     <section remap="h5">
       <title>Synopsis</title>
       <screen>lfs
-lfs changelog [--follow] &lt;mdtname&gt; [startrec [endrec]]
-lfs changelog_clear &lt;mdtname&gt; &lt;id&gt; &lt;endrec&gt;
-lfs check &lt;mds|osts|servers&gt;
-lfs df [-i] [-h] [--pool]-p &lt;fsname&gt;[.&lt;pool&gt;] [path]
-lfs find [[!] --atime|-A [-+]N] [[!] --mtime|-M [-+]N] 
-   [[!] --ctime|-C [-+]N] [--maxdepth|-D N] [--name|-n &lt;pattern&gt;]
-   [--print|-p] [--print0|-P] [[!] --obd|-O &lt;uuid[s]&gt;] 
-   [[!] --size|-S [+-]N[kMGTPE]] --type |-t {bcdflpsD}]
-   [[!] --gid|-g|--group|-G &lt;gname&gt;|&lt;gid&gt;]
-   [[!] --uid|-u|--user|-U &lt;uname&gt;|&lt;uid&gt;]
-   &lt;dirname|filename&gt;
+lfs changelog [--follow] <replaceable>mdt_name</replaceable> [startrec [endrec]]
+lfs changelog_clear <replaceable>mdt_name id endrec</replaceable>
+lfs check <replaceable>mds|osts|servers</replaceable>
+lfs df [-i] [-h] [--pool]-p <replaceable>fsname</replaceable>[.<replaceable>pool</replaceable>] [<replaceable>path</replaceable>] [--lazy]
+lfs find [[!] --atime|-A [-+]N] [[!] --mtime|-M [-+]N]
+         [[!] --ctime|-C [-+]N] [--maxdepth|-D N] [--name|-n <replaceable>pattern</replaceable>]
+         [--print|-p] [--print0|-P] [[!] --obd|-O <replaceable>ost_name</replaceable>[,<replaceable>ost_name...</replaceable>]]
+         [[!] --size|-S [+-]N[kMGTPE]] --type |-t {bcdflpsD}]
+         [[!] --gid|-g|--group|-G <replaceable>gname|gid</replaceable>]
+         [[!] --uid|-u|--user|-U <replaceable>uname|uid</replaceable>]
+         <replaceable>dirname|filename</replaceable>
+lfs getname [-h]|[path...]
+lfs getstripe [--obd|-O <replaceable>ost_name</replaceable>] [--quiet|-q] [--verbose|-v]
+              [--count|-c] [--index|-i | --offset|-o]
+              [--size|-s] [--pool|-p] [--directory|-d]
+              [--recursive|-r] [--raw|-R] [-M] <replaceable>dirname|filename</replaceable> ...
+lfs setstripe [--size|-s stripe_size] [--count|-c <replaceable>stripe_count</replaceable>]
+              [--index|-i|--offset|-o <replaceable>start_ost_index</replaceable>]
+              [--pool|-p <replaceable>pool</replaceable>]
+              <replaceable>dirname|filename</replaceable>
+lfs setstripe -d <replaceable>dir</replaceable>
 lfs osts [path]
-lfs getstripe [--obd|-O &lt;uuid&gt;] [--quiet|-q] [--verbose|-v]
-                   [--count|-c] [--index|-i | --offset|-o]
-                   [--size|-s] [--pool|-p] [--directory|-d]
-                   [--recursive|-r] &lt;dirname|filename&gt; ...
-lfs setstripe              [--size|-s stripe_size] [--count|-c stripe_cnt] 
-           [--index|-i|--offset|-o start_ost_index] 
-           [--pool|-p &lt;pool&gt;]
-           &lt;dirname|filename&gt;
-lfs setstripe -d &lt;dir&gt;
-lfs poollist &lt;filesystem&gt;[.&lt;pool&gt;]|&lt;pathname&gt;
-lfs quota [-q] [-v] [-o obd_uuid|-I ost_idx|-i mdt_idx] [-u &lt;uname&gt;| -u &lt;uid&gt;|-g &lt;gname&gt;| -g &lt;gid&gt;] &lt;filesystem&gt;
-lfs quota -t &lt;-u|-g&gt; &lt;filesystem&gt;
-lfs quotacheck [-ug] &lt;filesystem&gt;
-lfs quotachown [-i] &lt;filesystem&gt;
-lfs quotaon [-ugf] &lt;filesystem&gt;
-lfs quotaoff [-ug] &lt;filesystem&gt;
-lfs quotainv [-ug] [-f] &lt;filesystem&gt;
-lfs setquota               &lt;-u|--user|-g|--group&gt; &lt;uname|uid|gname|gid&gt;
-                   [--block-softlimit &lt;block-softlimit&gt;]
-                   [--block-hardlimit &lt;block-hardlimit&gt;]
-                   [--inode-softlimit &lt;inode-softlimit&gt;]
-                   [--inode-hardlimit &lt;inode-hardlimit&gt;]
-                   &lt;filesystem&gt;
-lfs setquota &lt;-u|--user|-g|--group&gt; &lt;uname|uid|gname|gid&gt;
-           [-b &lt;block-softlimit&gt;] [-B &lt;block-hardlimit&gt;]
-           [-i &lt;inode-softlimit&gt;] [-I &lt;inode-hardlimit&gt;] 
-           &lt;filesystem&gt;
-lfs setquota -t &lt;-u|-g&gt;
-           [--block-grace &lt;block-grace&gt;]
-           [--inode-grace &lt;inode-grace&gt;]
-           &lt;filesystem&gt;
-lfs setquota -t &lt;-u|-g&gt;
-           [-b &lt;block-grace&gt;] [-i &lt;inode-grace&gt;]
-           &lt;filesystem&gt;
+lfs poollist <replaceable>filesystem</replaceable>[.<replaceable>pool</replaceable>]|<replaceable>pathname</replaceable>
+lfs quota [-q] [-v] [-h] [-o <replaceable>obd_uuid</replaceable>|-I <replaceable>ost_idx</replaceable>|-i <replaceable>mdt_idx</replaceable>]
+          [-u <replaceable>username|uid|-g</replaceable> <replaceable>group|gid</replaceable>]
+          <replaceable>/mount_point</replaceable>
+lfs quota -t -u|-g <replaceable>/mount_point</replaceable>
+lfs quotacheck [-ug] <replaceable>/mount_point</replaceable>
+lfs quotachown [-i] <replaceable>/mount_point</replaceable>
+lfs quotainv [-ug] [-f] <replaceable>/mount_point</replaceable>
+lfs quotaon [-ugf] <replaceable>/mount_point</replaceable>
+lfs quotaoff [-ug] <replaceable>/mount_point</replaceable>
+lfs setquota {-u|--user|-g|--group} <replaceable>uname|uid|gname|gid</replaceable>
+             [--block-softlimit <replaceable>block_softlimit</replaceable>]
+             [--block-hardlimit <replaceable>block_hardlimit</replaceable>]
+             [--inode-softlimit <replaceable>inode_softlimit</replaceable>]
+             [--inode-hardlimit <replaceable>inode_hardlimit</replaceable>]
+             <replaceable>/mount_point</replaceable>
+lfs setquota -u|--user|-g|--group <replaceable>uname|uid|gname|gid</replaceable>
+             [-b <replaceable>block_softlimit</replaceable>] [-B <replaceable>block_hardlimit</replaceable>]
+             [-i <replaceable>inode-softlimit</replaceable>] [-I <replaceable>inode_hardlimit</replaceable>]
+             <replaceable>/mount_point</replaceable>
+lfs setquota -t -u|-g
+             [--block-grace <replaceable>block_grace</replaceable>]
+             [--inode-grace <replaceable>inode_grace</replaceable>]
+             <replaceable>/mount_point</replaceable>
+lfs setquota -t -u|-g
+             [-b <replaceable>block_grace</replaceable>] [-i <replaceable>inode_grace</replaceable>]
+             <replaceable>/mount_point</replaceable>
 lfs help
 </screen>
       <note>
-        <para>In the above example, the <literal>&lt;filesystem&gt;</literal> parameter refers to the mount point of the Lustre file system. The default mount point is <literal>/mnt/lustre</literal></para>
+        <para>In the above example, the <literal><replaceable>/mount_point</replaceable></literal> parameter refers to the mount point of the Lustre file system.</para>
       </note>
       <note>
         <para>The old lfs quota output was very detailed and contained cluster-wide quota statistics (including cluster-wide limits for a user/group and cluster-wide usage for a user/group), as well as statistics for each MDS/OST. Now, <literal>lfs quota</literal> has been updated to provide only cluster-wide statistics, by default. To obtain the full report of cluster-wide limits, usage and statistics, use the <literal>-v</literal> option with <literal>lfs quota</literal>.</para>
@@ -94,9 +93,9 @@ lfs help
       <para>The various <literal>lfs</literal> options are listed and described below. For a complete list of available options, type help at the <literal>lf</literal>s prompt.</para>
       <informaltable frame="all">
         <tgroup cols="3">
-          <colspec colname="c1" colwidth="33*"/>
-          <colspec colname="c2" colwidth="33*"/>
-          <colspec colname="c3" colwidth="33*"/>
+          <colspec colname="c1" colwidth="20*"/>
+          <colspec colname="c2" colwidth="30*"/>
+          <colspec colname="c3" colwidth="50*"/>
           <thead>
             <row>
               <entry nameend="c2" namest="c1">
@@ -121,7 +120,7 @@ lfs help
                 <para> <literal>changelog_clear</literal></para>
               </entry>
               <entry>
-                <para>Indicates that changelog records previous to <literal>&lt;endrec&gt;</literal> are no longer of interest to a particular consumer <literal>&lt;id&gt;</literal>, potentially allowing the MDT to free up disk space. An <literal>&lt;endrec&gt;</literal> of 0 indicates the current last record. Changelog consumers must be registered on the MDT node using <literal>lctl</literal>.</para>
+                <para>Indicates that changelog records previous to <literal><replaceable>endrec</replaceable></literal> are no longer of interest to a particular consumer <literal><replaceable>id</replaceable></literal>, potentially allowing the MDT to free up disk space. An <literal><replaceable>endrec</replaceable></literal> of 0 indicates the current last record. Changelog consumers must be registered on the MDT node using <literal>lctl</literal>.</para>
               </entry>
             </row>
             <row>
@@ -134,10 +133,28 @@ lfs help
             </row>
             <row>
               <entry nameend="c2" namest="c1">
-                <literal> df [-i] [-h] [--pool|-p &lt;fsname&gt;[.&lt;pool&gt;] [path] </literal>
-              </entry>
-              <entry>
-                <para>Report file system disk space usage or inode usage (with <literal>-i</literal>) of each MDT/OST or a subset of OSTs if a pool is specified with <literal>-p</literal>. By default, prints the usage of all mounted Lustre file systems. Otherwise, if path is specified, prints only the usage of that file system. If <literal>-h</literal> is given, the output is printed in human-readable format, using SI base-2 suffixes for <emphasis role="bold">M</emphasis>ega-, <emphasis role="bold">G</emphasis>iga-, <emphasis role="bold">T</emphasis>era-, <emphasis role="bold">P</emphasis>eta-, or <emphasis role="bold">E</emphasis>xabytes.</para>
+                <literal> df [-i] [-h] [--pool|-p
+                    <replaceable>fsname</replaceable>[.<replaceable>pool</replaceable>]
+                    [<replaceable>path</replaceable>] [--lazy]</literal>
+              </entry>
+              <entry>
+                <para>Use <literal>-i</literal> to report file system disk space usage or inode
+                  usage of each MDT or OST or, if a pool is specified with the <literal>-p</literal>
+                  option, a subset of OSTs.</para>
+                <para>By default, the usage of all mounted Lustre file systems is reported. If the
+                    <literal>path</literal> option is included, only the usage for the specified
+                  file system is reported. If the <literal>-h</literal> option is included, the
+                  output is printed in human-readable format, using SI base-2 suffixes for <emphasis
+                    role="bold">M</emphasis>ega-, <emphasis role="bold">G</emphasis>iga-, <emphasis
+                    role="bold">T</emphasis>era-, <emphasis role="bold">P</emphasis>eta-, or
+                    <emphasis role="bold">E</emphasis>xabytes.</para>
+                <para>If the <literal>--lazy</literal> option is specified, any OST that is
+                  currently disconnected from the client will be skipped. Using the
+                    <literal>--lazy</literal> option prevents the <literal>df</literal> output from
+                  being blocked when  an OST is offline. Only the space on the OSTs that can
+                  currently be accessed are returned. The <literal>llite.*.lazystatfs</literal>
+                  tunable can be enabled to make this the default behaviour for all
+                    <literal>statfs()</literal> operations.</para>
               </entry>
             </row>
             <row>
@@ -156,7 +173,13 @@ lfs help
               </entry>
               <entry>
                 <para>File was last accessed N*24 hours ago. (There is no guarantee that <literal>atime</literal> is kept coherent across the cluster.)</para>
-                <para>OSTs store a transient <literal>atime</literal> that is updated when clients do read requests. Permanent <literal>atime</literal> is written to the MDS when the file is closed. However, on-disk atime is only updated if it is more than 60 seconds old (<literal>/proc/fs/lustre/mds/*/max_atime_diff</literal>). Lustre considers the latest <literal>atime</literal> from all OSTs. If a <literal>setattr</literal> is set by user, then it is updated on both the MDS and OST, allowing the <literal>atime</literal> to go backward.</para>
+                <para>OSTs store a transient <literal>atime</literal> that is updated when clients
+                  do read requests. Permanent <literal>atime</literal> is written to the MDS when
+                  the file is closed. However, on-disk atime is only updated if it is more than 60
+                  seconds old (<literal>/proc/fs/lustre/mds/*/max_atime_diff</literal>). The Lustre
+                  software considers the latest <literal>atime</literal> from all OSTs. If a
+                    <literal>setattr</literal> is set by user, then it is updated on both the MDS
+                  and OST, allowing the <literal>atime</literal> to go backward.</para>
               </entry>
             </row>
             <row>
@@ -211,7 +234,8 @@ lfs help
                 <para> <literal>--type</literal></para>
               </entry>
               <entry>
-                <para>File has the type (block, character, directory, pipe, file, symlink, socket or Door [Solaris]).</para>
+                <para>File has the type  - block, character, directory, pipe, file, symlink, socket
+                  or door (used in Solaris operating system).</para>
               </entry>
             </row>
             <row>
@@ -285,7 +309,20 @@ lfs help
                 <para> <literal>osts [path]</literal></para>
               </entry>
               <entry>
-                <para>Lists all OSTs for the file system. If a path located on a Lustre-mounted file system is specified, then only OSTs belonging to this file system are displayed.</para>
+                <para>Lists all OSTs for the file system. If a path located on a mounted Lustre file
+                  system is specified, then only OSTs belonging to this file system are
+                  displayed.</para>
+              </entry>
+            </row>
+            <row>
+              <entry nameend="c2" namest="c1">
+                <para> <literal>getname [path...]</literal></para>
+              </entry>
+              <entry>
+                  <para>List each Lustre file system instance associated with each Lustre mount
+                  point. If no path is specified, all Lustre mount points are interrogated. If a
+                  list of paths is provided, the instance of each path is provided. If the path is
+                  not a Lustre instance 'No such device' is returned.</para>
               </entry>
             </row>
             <row>
@@ -295,6 +332,11 @@ lfs help
               <entry>
                 <para>Lists striping information for a given filename or directory. By default, the stripe count, stripe size and offset are returned.</para>
                 <para>If you only want specific striping information, then the options of <literal>--count</literal>,<literal>--size</literal>,<literal>--index</literal> or <literal>--offset</literal> plus various combinations of these options can be used to retrieve specific information.</para>
+                <para>If the <literal>--raw</literal> option is specified, the stripe information is
+                  printed without substituting the file system default values for unspecified
+                  fields. If the striping EA is not set, 0, 0, and -1 will be printed for the stripe
+                  count, size, and offset respectively.</para>
+                               <para condition='l24'>The <literal>-M</literal> prints the index of the MDT for a given directory. See <xref linkend='dbdoclet.rmremotedir'/>.</para>
               </entry>
             </row>
             <row>
@@ -302,7 +344,7 @@ lfs help
                 <para> &#160;</para>
               </entry>
               <entry>
-                <para> <literal>--obd &lt;uuid&gt;</literal></para>
+                <para> <literal>--obd <replaceable>ost_name</replaceable></literal></para>
               </entry>
               <entry>
                 <para>Lists files that have an object on a specific OST.</para>
@@ -425,7 +467,7 @@ lfs help
                 <para> <literal>--count stripe_cnt</literal></para>
               </entry>
               <entry>
-                <para>Number of OSTs over which to stripe a file. A <literal>stripe_cnt</literal> of 0 uses the file system-wide default stripe count (default is 1). A <literal>stripe_cnt</literal> of -1 stripes over all available OSTs, and normally results in a file with 80 stripes.</para>
+                <para>Number of OSTs over which to stripe a file. A <literal>stripe_cnt</literal> of 0 uses the file system-wide default stripe count (default is 1). A <literal>stripe_cnt</literal> of -1 stripes over all available OSTs.</para>
               </entry>
             </row>
             <row>
@@ -457,7 +499,7 @@ lfs help
                 <para> &#160;</para>
               </entry>
               <entry>
-                <para> <literal>--pool &lt;pool&gt;</literal></para>
+                <para> <literal>--pool <replaceable>pool</replaceable></literal></para>
               </entry>
               <entry>
                 <para>Name of the pre-defined pool of OSTs (see <xref linkend="dbdoclet.50438219_38274"/>) that will be used for striping. The <literal>stripe_cnt</literal>, <literal>stripe_size</literal> and <literal>start_ost</literal> values are used as well. The start-ost value must be part of the pool or an error is returned.</para>
@@ -481,7 +523,7 @@ lfs help
             </row>
             <row>
               <entry nameend="c2" namest="c1">
-                <para> <literal>quota [-q] [-v] [-o obd_uuid|-i mdt_idx|-I ost_idx] [-u|-g &lt;uname&gt;|&lt;uid&gt;|&lt;gname&gt;|&lt;gid&gt;] &lt;filesystem&gt;</literal></para>
+                <para> <literal>quota [-q] [-v] [-o <replaceable>obd_uuid</replaceable>|-i <replaceable>mdt_idx</replaceable>|-I <replaceable>ost_idx</replaceable>] [-u|-g <replaceable>uname|uid|gname|gid]</replaceable> <replaceable>/mount_point</replaceable></literal></para>
                 <para>&#160;</para>
               </entry>
               <entry>
@@ -490,7 +532,7 @@ lfs help
             </row>
             <row>
               <entry nameend="c2" namest="c1">
-                <para> <literal>quota -t &lt;-u|-g&gt; &lt;filesystem&gt;</literal></para>
+                <para> <literal>quota -t <replaceable>-u|-g</replaceable> <replaceable>/mount_point</replaceable></literal></para>
               </entry>
               <entry>
                 <para>Displays block and inode grace times for user (<literal>-u</literal>) or group (<literal>-g</literal>) quotas.</para>
@@ -506,7 +548,7 @@ lfs help
             </row>
             <row>
               <entry nameend="c2" namest="c1">
-                <para> <literal>quotacheck [-ugf] &lt;filesystem&gt;</literal></para>
+                <para> <literal>quotacheck [-ugf] <replaceable>/mount_point</replaceable></literal></para>
               </entry>
               <entry>
                 <para>Scans the specified file system for disk usage, and creates or updates quota files. Options specify quota for users (<literal>-u</literal>), groups (<literal>-g</literal>), and force (<literal>-f</literal>).</para>
@@ -514,7 +556,7 @@ lfs help
             </row>
             <row>
               <entry nameend="c2" namest="c1">
-                <para> <literal>quotaon [-ugf] &lt;filesystem&gt;</literal></para>
+                <para> <literal>quotaon [-ugf] <replaceable>/mount_point</replaceable></literal></para>
               </entry>
               <entry>
                 <para>Turns on file system quotas. Options specify quota for users (<literal>-u</literal>), groups (<literal>-g</literal>), and force (<literal>-f</literal>).</para>
@@ -522,7 +564,7 @@ lfs help
             </row>
             <row>
               <entry nameend="c2" namest="c1">
-                <para> <literal>quotaoff [-ugf] &lt;filesystem&gt;</literal></para>
+                <para> <literal>quotaoff [-ugf] <replaceable>/mount_point</replaceable></literal></para>
               </entry>
               <entry>
                 <para>Turns off file system quotas. Options specify quota for users (<literal>-u</literal>), groups (<literal>-g</literal>), and force (<literal>-f</literal>).</para>
@@ -530,7 +572,7 @@ lfs help
             </row>
             <row>
               <entry nameend="c2" namest="c1">
-                <para> <literal>quotainv [-ug] [-f] &lt;filesystem&gt;</literal></para>
+                <para> <literal>quotainv [-ug] [-f] <replaceable>/mount_point</replaceable></literal></para>
               </entry>
               <entry>
                 <para> Clears quota files (administrative quota files if used without <literal>-f</literal>, operational quota files otherwise), all of their quota entries for users (<literal>-u</literal>) or groups (<literal>-g</literal>). After running <literal>quotainv</literal>, you must run <literal>quotacheck</literal> before using quotas.</para>
@@ -541,17 +583,18 @@ lfs help
             </row>
             <row>
               <entry nameend="c2" namest="c1">
-                <para> <literal>setquota &lt;-u|-g&gt; &lt;uname&gt;|&lt;uid&gt;|&lt;gname&gt;|&lt;gid&gt; [--block-softlimit &lt;block-softlimit&gt;] [--block-hardlimit &lt;block-hardlimit&gt;] [--inode-softlimit &lt;inode-softlimit&gt;] [--inode-hardlimit &lt;inode-hardlimit&gt;] &lt;filesystem&gt;</literal></para>
+                <para> <literal>setquota -u|-g <replaceable>uname|uid|gname|gid}</replaceable> [--block-softlimit <replaceable>block_softlimit</replaceable>] [--block-hardlimit <replaceable>block_hardlimit</replaceable>] [--inode-softlimit <replaceable>inode_softlimit</replaceable>] [--inode-hardlimit <replaceable>inode_hardlimit</replaceable>] <replaceable>/mount_point</replaceable></literal></para>
               </entry>
               <entry>
                 <para>Sets file system quotas for users or groups. Limits can be specified with <literal>--{block|inode}-{softlimit|hardlimit}</literal> or their short equivalents <literal>-b</literal>, <literal>-B</literal>, <literal>-i</literal>, <literal>-I</literal>. Users can set 1, 2, 3 or 4 limits.<footnote>
-                    <para>The old <literal>setquota</literal> interface is supported, but it may be removed in a future Lustre release.</para>
+                    <para>The old <literal>setquota</literal> interface is supported, but it may be
+                      removed in a future Lustre software release.</para>
                   </footnote>Also, limits can be specified with special suffixes, -b, -k, -m, -g, -t, and -p to indicate units of 1, 2^10, 2^20, 2^30, 2^40 and 2^50, respectively. By default, the block limits unit is 1 kilobyte (1,024), and block limits are always kilobyte-grained (even if specified in bytes). See <xref linkend="dbdoclet.50438206_11903"/>.</para>
               </entry>
             </row>
             <row>
               <entry nameend="c2" namest="c1">
-                <para><literal> setquota -t &lt;-u|-g&gt; [--block-grace &lt;block-grace&gt;] [--inode-grace &lt;inode-grace&gt;] &lt;filesystem&gt;</literal></para>
+                <para><literal> setquota -t -u|-g [--block-grace <replaceable>block_grace</replaceable>] [--inode-grace <replaceable>inode_grace</replaceable>] <replaceable>/mount_point</replaceable></literal></para>
               </entry>
               <entry>
                 <para>Sets the file system quota grace times for users or groups. Grace time is specified in &apos;<literal>XXwXXdXXhXXmXXs</literal>&apos; format or as an integer seconds value. See <xref linkend="dbdoclet.50438206_11903"/>.</para>
@@ -585,6 +628,8 @@ lfs help
       <screen>$ lfs setstripe -d /mnt/lustre/dir</screen>
       <para>Lists the detailed object allocation of a given file.</para>
       <screen>$ lfs getstripe -v /mnt/lustre/file1</screen>
+      <para>List all the mounted Lustre file systems and corresponding Lustre instances.</para>
+      <screen>$ lfs getname</screen>
       <para>Efficiently lists all files in a given directory and its subdirectories.</para>
       <screen>$ lfs find /mnt/lustre</screen>
       <para>Recursively lists all regular files in a given directory more than 30 days old.</para>
@@ -598,10 +643,10 @@ lfs help
       <para>Lists inode usage per OST and MDT.</para>
       <screen>$ lfs df -i</screen>
       <para>List space or inode usage for a specific OST pool.</para>
-      <screen>$ lfs df --pool &lt;filesystem&gt;[.&lt;pool&gt;] | &lt;pathname&gt;</screen>
+      <screen>$ lfs df --pool <replaceable>filesystem</replaceable>[.<replaceable>pool</replaceable>] | <replaceable>pathname</replaceable></screen>
       <para>List quotas of user &apos;bob&apos;.</para>
       <screen>$ lfs quota -u bob /mnt/lustre</screen>
-      <para>Show grace times for user quotas on /mnt/lustre.</para>
+      <para>Show grace times for user quotas on <literal>/mnt/lustre</literal>.</para>
       <screen>$ lfs quota -t -u /mnt/lustre</screen>
       <para>Changes file owner and group.</para>
       <screen>$ lfs quotachown -i /mnt/lustre</screen>
@@ -644,7 +689,7 @@ lfs help
     <para>The <literal>lfs_migrate</literal> utility is a simple tool to migrate files between Lustre OSTs.</para>
     <section remap="h5">
       <title>Synopsis</title>
-      <screen>lfs_migrate [-c|-s] [-h] [-l] [-n] [-y] [file|directory ...]</screen>
+      <screen>lfs_migrate [-c <replaceable>stripecount</replaceable>] [-h] [-l] [-n] [-q] [-R] [-s] [-y] [file|directory ...]</screen>
     </section>
     <section remap="h5">
       <title>Description</title>
@@ -673,26 +718,21 @@ lfs help
           <tbody>
             <row>
               <entry>
-                <para> <literal>-c</literal></para>
+                <para>
+                  <literal>-c <replaceable>stripecount</replaceable></literal></para>
               </entry>
               <entry>
-                <para>Compares file data after migrate (default value, use <literal>-s</literal> to disable).</para>
+                <para>Restripe file using the specified stripe count. This option may not be
+                  specified at the same time as the <literal>-R</literal> option.</para>
               </entry>
             </row>
             <row>
               <entry>
-                <para> <literal>-s</literal></para>
+                <para>
+                  <literal>-h</literal></para>
               </entry>
               <entry>
-                <para>Skips file data comparison after migrate (use <literal>-c</literal> to enable).</para>
-              </entry>
-            </row>
-            <row>
-              <entry>
-                <para> <literal>-h</literal></para>
-              </entry>
-              <entry>
-                <para>Displays help information.</para>
+                <para>Display help information.</para>
               </entry>
             </row>
             <row>
@@ -700,7 +740,9 @@ lfs help
                 <literal>-l</literal>
               </entry>
               <entry>
-                <para>Migrates files with hard links (skips, by default). Files with multiple hard links are split into multiple separate files by <literal>lfs_migrate</literal>, so they are skipped, by default, to avoid breaking the hard links.</para>
+                <para>Migrate files with hard links (skips, by default). Files with multiple hard
+                  links are split into multiple separate files by <literal>lfs_migrate</literal>, so
+                  they are skipped, by default, to avoid breaking the hard links.</para>
               </entry>
             </row>
             <row>
@@ -708,7 +750,7 @@ lfs help
                 <literal>-n</literal>
               </entry>
               <entry>
-                <para>Only prints the names of files to be migrated.</para>
+                <para>Only print the names of files to be migrated.</para>
               </entry>
             </row>
             <row>
@@ -716,15 +758,29 @@ lfs help
                 <para> <literal>-q</literal></para>
               </entry>
               <entry>
-                <para>Runs quietly (does not print filenames or status).</para>
+                <para>Run quietly (does not print filenames or status).</para>
               </entry>
             </row>
             <row>
+              <entry><literal>-R</literal></entry>
+              <entry>Restripe file using default directory striping instead of keeping striping.
+                This option may not be specified at the same time as the <literal>-c</literal>
+                option.</entry>
+            </row>
+            <row>
+              <entry>
+                <literal>-s</literal></entry>
+              <entry>Skip file data comparison after migrate. Default is to compare migrated file
+                against original to verify correctness.</entry>
+            </row>
+            <row>
               <entry>
-                <para> <literal>--y</literal></para>
+                <para>
+                  <literal>-y</literal></para>
               </entry>
               <entry>
-                <para>Answers &apos;<literal>y</literal>&apos; to usage warning without prompting (for scripts).</para>
+                <para>Answer &apos;<literal>y</literal>&apos; to usage warning without prompting
+                  (for scripts, use with caution).</para>
               </entry>
             </row>
           </tbody>
@@ -743,117 +799,6 @@ lfs help
       <para><xref linkend="dbdoclet.50438206_94597"/></para>
     </section>
   </section>
-  <section xml:id="dbdoclet.50438206_91700">
-    <title><indexterm><primary>lfsck</primary></indexterm>
-       <literal>lfsck</literal>
-    </title>
-    <para><literal>lfsck</literal> ensures that objects are not referenced by multiple MDS files, that there are no orphan objects on the OSTs (objects that do not have any file on the MDS which references them), and that all of the objects referenced by the MDS exist. Under normal circumstances, Lustre maintains such coherency by distributed logging mechanisms, but under exceptional circumstances that may fail (e.g. disk failure, file system corruption leading to e2fsck repair). To avoid lengthy downtime, you can also run <literal>lfsck</literal> once Lustre is already started.</para>
-    <para>The <literal>e2fsck</literal> utility is run on each of the local MDS and OST device file systems and verifies that the underlying <literal>ldiskfs</literal> is consistent. After <literal>e2fsck</literal> is run, <literal>lfsck</literal> does distributed coherency checking for the Lustre file system. In most cases, <literal>e2fsck</literal> is sufficient to repair any file system issues and <literal>lfsck</literal> is not required.</para>
-    <section remap="h5">
-      <title>Synopsis</title>
-      <screen>lfsck [-c|--create] [-d|--delete] [-f|--force] [-h|--help] [-l|--lostfound] [-n|--nofix] [-v|--verbose] --mdsdb mds_database_file --ostdb ost1_database_file [ost2_database_file...] &lt;filesystem&gt;
-</screen>
-      <note>
-        <para>As shown, the <literal>&lt;filesystem&gt;</literal> parameter refers to the Lustre file system mount point. The default mount point is <literal>/mnt/lustre</literal>.</para>
-      </note>
-      <note>
-        <para>For <literal>lfsck</literal>, database filenames must be provided as absolute pathnames. Relative paths do not work, the databases cannot be properly opened.</para>
-      </note>
-    </section>
-    <section remap="h5">
-      <title>Options</title>
-      <para>The options and descriptions for the <literal>lfsck</literal> command are listed below.</para>
-      <informaltable frame="all">
-        <tgroup cols="2">
-          <colspec colname="c1" colwidth="50*"/>
-          <colspec colname="c2" colwidth="50*"/>
-          <thead>
-            <row>
-              <entry>
-                <para><emphasis role="bold">Option</emphasis></para>
-              </entry>
-              <entry>
-                <para><emphasis role="bold">Description</emphasis></para>
-              </entry>
-            </row>
-          </thead>
-          <tbody>
-            <row>
-              <entry>
-                <para> <literal>-c</literal></para>
-              </entry>
-              <entry>
-                <para>Creates (empty) missing OST objects referenced by MDS inodes.</para>
-              </entry>
-            </row>
-            <row>
-              <entry>
-                <para> <literal>-d</literal></para>
-              </entry>
-              <entry>
-                <para>Deletes orphaned objects from the file system. Since objects on the OST are often only one of several stripes of a file, it can be difficult to compile multiple objects together in a single, usable file.</para>
-              </entry>
-            </row>
-            <row>
-              <entry>
-                <para> <literal>-h</literal></para>
-              </entry>
-              <entry>
-                <para>Prints a brief help message.</para>
-              </entry>
-            </row>
-            <row>
-              <entry>
-                <para> <literal>-l</literal></para>
-              </entry>
-              <entry>
-                <para>Puts orphaned objects into a <literal>lost+found</literal> directory in the root of the file system.</para>
-              </entry>
-            </row>
-            <row>
-              <entry>
-                <para> <literal>-n</literal></para>
-              </entry>
-              <entry>
-                <para>Does not repair the file system, just performs a read-only check (default).</para>
-              </entry>
-            </row>
-            <row>
-              <entry>
-                <para> <literal>-v</literal></para>
-              </entry>
-              <entry>
-                <para>Verbose operation - more verbosity by specifying the option multiple times.</para>
-              </entry>
-            </row>
-            <row>
-              <entry>
-                <para> <literal>--mdsdb</literal></para>
-                <para><literal>mds_database_file</literal></para>
-              </entry>
-              <entry>
-                <para>MDS database file created by running <literal>e2fsck</literal> <literal>--mdsdb</literal> <literal>mds_database_file</literal> <literal>&lt;device&gt;</literal> on the MDS backing device. This is required.</para>
-              </entry>
-            </row>
-            <row>
-              <entry>
-                <para> <literal>--ostdb ost1_database_file</literal></para>
-                <para><literal>[ost2_database_file...]</literal></para>
-              </entry>
-              <entry>
-                <para>OST database files created by running <literal>e2fsck</literal> <literal>--ostdb ost_database_file &lt;device&gt;</literal> on each of the OST backing devices. These are required unless an OST is unavailable, in which case all objects thereon are considered missing.</para>
-              </entry>
-            </row>
-          </tbody>
-        </tgroup>
-      </informaltable>
-    </section>
-    <section remap="h5">
-      <title>Description</title>
-      <para>The <literal>lfsck</literal> utility is used to check and repair the distributed coherency of a Lustre file system. If an MDS or an OST becomes corrupt, run a distributed check on the file system to determine what sort of problems exist. Use lfsck to correct any defects found.</para>
-      <para>For more information on using <literal>e2fsck</literal> and <literal>lfsck</literal>, including examples, see <xref linkend="dbdoclet.50438268_83826"/> (Commit on Share). For information on resolving orphaned objects, see <xref linkend="dbdoclet.50438225_13916"/> (Working with Orphaned Objects).</para>
-    </section>
-  </section>
   <section xml:id="dbdoclet.50438206_75125">
     <title><indexterm><primary>filefrag</primary></indexterm>
       <literal>filefrag</literal>
@@ -867,11 +812,15 @@ lfs help
       <title>Description</title>
       <para>The <literal>filefrag</literal> utility reports the extent of fragmentation in a given file. Initially, <literal>filefrag</literal> attempts to obtain extent information using <literal>FIEMAP ioctl</literal>, which is efficient and fast. If <literal>FIEMAP</literal> is not supported, then <literal>filefrag</literal> uses <literal>FIBMAP</literal>.</para>
       <note>
-        <para>Lustre only supports <literal>FIEMAP ioctl</literal>. <literal>FIBMAP ioctl</literal> is not supported.</para>
+        <para>The Lustre software only supports <literal>FIEMAP ioctl</literal>. <literal>FIBMAP
+            ioctl</literal> is not supported.</para>
       </note>
       <para>In default mode <footnote>
           <para>The default mode is faster than the verbose/extent mode.</para>
-        </footnote>, <literal>filefrag</literal> returns the number of physically discontiguous extents in the file. In extent or verbose mode, each extent is printed with details. For Lustre, the extents are printed in device offset order, not logical offset order.</para>
+        </footnote>, <literal>filefrag</literal> returns the number of physically discontiguous
+        extents in the file. In extent or verbose mode, each extent is printed with details. For a
+        Lustre file system, the extents are printed in device offset order, not logical offset
+        order.</para>
     </section>
     <section remap="h5">
       <title>Options</title>
@@ -896,7 +845,8 @@ lfs help
                 <para> <literal>-b</literal></para>
               </entry>
               <entry>
-                <para>Uses the 1024-byte blocksize for the output. By default, this blocksize is used by Lustre, since OSTs may use different block sizes.</para>
+                <para>Uses the 1024-byte blocksize for the output. By default, this blocksize is
+                  used by the Lustre file system, since OSTs may use different block sizes.</para>
               </entry>
             </row>
             <row>
@@ -960,7 +910,10 @@ ext:       device_logical:         start..end              physical:
     <title><indexterm><primary>mount</primary></indexterm>
       <literal>mount</literal>
     </title>
-    <para>Lustre uses the standard <literal>mount(8)</literal> Linux command. When mounting a Lustre file system, mount(8) executes the <literal>/sbin/mount.lustre</literal> command to complete the mount. The mount command supports these Lustre-specific options:</para>
+    <para>The standard <literal>mount(8)</literal> Linux command is used to mount a Lustre file
+      system. When mounting a Lustre file system, mount(8) executes the
+        <literal>/sbin/mount.lustre</literal> command to complete the mount. The mount command
+      supports these options specific to a Lustre file system:</para>
     <informaltable frame="all">
       <tgroup cols="2">
         <colspec colname="c1" colwidth="50*"/>
@@ -994,12 +947,28 @@ ext:       device_logical:         start..end              physical:
           </row>
           <row>
             <entry>
+              <para> <literal>nomgs</literal></para>
+            </entry>
+            <entry>
+              <para>Start a MDT with a co-located MGS without starting the MGS</para>
+            </entry>
+          </row>
+          <row>
+            <entry>
               <para> <literal>exclude</literal></para>
             </entry>
             <entry>
               <para>Starts with a dead OST</para>
             </entry>
           </row>
+          <row>
+            <entry>
+              <para> <literal>md_stripe_cache_size</literal></para>
+            </entry>
+            <entry>
+              <para>Sets the stripe cache size for server side disk with a striped raid configuration</para>
+            </entry>
+          </row>
         </tbody>
       </tgroup>
     </informaltable>
@@ -1020,10 +989,10 @@ ext:       device_logical:         start..end              physical:
         <tbody>
           <row>
             <entry>
-              <para> <literal>flock</literal></para>
+              <para> <literal>flock/noflock/localflock</literal></para>
             </entry>
             <entry>
-              <para>Enables/disables flock support</para>
+              <para>Enables/disables global flock or local flock support</para>
             </entry>
           </row>
           <row>
@@ -1036,6 +1005,14 @@ ext:       device_logical:         start..end              physical:
           </row>
           <row>
             <entry>
+              <para> <literal>user_fid2path/nouser_fid2path</literal></para>
+            </entry>
+            <entry>
+              <para condition='l23'>Enables/disables FID to path translation by regular users</para>
+            </entry>
+          </row>
+          <row>
+            <entry>
               <para> <literal>retry=</literal></para>
             </entry>
             <entry>