+ <section remap="h5">
+ <title>Options</title>
+ <para>The various
+ <literal>lfs</literal> options are listed and described below. For a
+ complete list of available options, type help at the
+ <literal>lfs</literal> prompt.</para>
+ <informaltable frame="all">
+ <tgroup cols="3">
+ <colspec colname="c1" colwidth="20*" />
+ <colspec colname="c2" colwidth="30*" />
+ <colspec colname="c3" colwidth="50*" />
+ <thead>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <emphasis role="bold">Option</emphasis>
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <emphasis role="bold">Description</emphasis>
+ </para>
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>changelog</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Shows the metadata changes on an MDT. Start and end
+ points are optional. The
+ <literal>--follow</literal> option blocks on new changes; this
+ option is only valid when run directly on the MDT node.</para>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>changelog_clear</literal>
+ </para>
+ </entry>
+ <entry>
+ <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>
+ <entry nameend="c2" namest="c1">
+ <literal>check</literal>
+ </entry>
+ <entry>
+ <para>Displays the status of MDS or OSTs (as specified in the
+ command) or all servers (MDS and OSTs).</para>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>data_version [-nrw]
+ <replaceable>filename</replaceable></literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Displays the current version of file data. If
+ <literal>-n</literal> is specified, the data version is read
+ without taking a lock. As a consequence, the data version could
+ be outdated if there are dirty caches on filesystem clients, but
+ this option will not force data flushes and has less of an
+ impact on the filesystem. If <literal>-r</literal> is specified,
+ the data version is read after dirty pages on clients are
+ flushed. If <literal>-w</literal> is specified, the data version
+ is read after all caching pages on clients are flushed.
+ </para>
+ <para>
+ Even with <literal>-r</literal> or <literal>-w</literal>, race
+ conditions are possible and the data version should be checked
+ before and after an operation to be confident the data did not
+ change during it.
+ </para>
+ <para>
+ The data version is the sum of the last committed transaction
+ numbers of all data objects of a file. It is used by HSM policy
+ engines for verifying that file data has not been changed during
+ an archive operation or before a release operation, and by OST
+ migration, primarily for verifying that file data has not been
+ changed during a data copy, when done in non-blocking mode.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <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>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>find</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Searches the directory tree rooted at the given
+ directory/filename for files that match the given
+ parameters.</para>
+ <para>Using
+ <literal>!</literal> before an option negates its meaning (files
+ NOT matching the parameter). Using
+ <literal>+</literal> before a numeric value means files with the
+ parameter OR MORE. Using
+ <literal>-</literal> before a numeric value means files with the
+ parameter OR LESS.</para>
+ </entry>
+ </row>
+ <row>
+ <entry />
+ <entry>
+ <literal>--atime</literal>
+ </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>). 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>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--ctime</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>File status was last changed N*24 hours ago.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--mtime</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>File data was last modified N*24 hours ago.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--obd</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>File has an object on a specific OST(s).</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--size</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>File has a size in bytes, or kilo-, Mega-, Giga-, Tera-,
+ Peta- or Exabytes if a suffix is given.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--type</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>File has the type - block, character, directory, pipe,
+ file, symlink, socket or door (used in Solaris operating
+ system).</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--uid</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>File has a specific numeric user ID.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--user</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>File owned by a specific user (numeric user ID
+ allowed).</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--gid</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>File has a specific group ID.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--group</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>File belongs to a specific group (numeric group ID
+ allowed).</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>-
+ <literal>-maxdepth</literal></para>
+ </entry>
+ <entry>
+ <para>Limits find to descend at most N levels of the directory
+ tree.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--print</literal>/
+ <literal>--print0</literal></para>
+ </entry>
+ <entry>
+ <para>Prints the full filename, followed by a new line or NULL
+ character correspondingly.</para>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>osts [path]</literal>
+ </para>
+ </entry>
+ <entry>
+ <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>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>getstripe</literal>
+ </para>
+ </entry>
+ <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>--stripe-count</literal>,
+ <literal>--stripe-size</literal>,
+ <literal>--stripe-index</literal>,
+ <literal>--layout</literal>, or
+ <literal>--pool</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>--mdt-index</literal> prints the index of the MDT for a given
+ directory. See
+ <xref linkend="dbdoclet.rmremotedir" />.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--obd
+ <replaceable>ost_name</replaceable></literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Lists files that have an object on a specific OST.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--quiet</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Lists details about the file's object ID
+ information.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--verbose</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Prints additional striping information.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--count</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Lists the stripe count (how many OSTs to use).</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--index</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Lists the index for each OST in the file system.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--offset</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Lists the OST index on which file striping starts.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--pool</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Lists the pools to which a file belongs.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--size</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Lists the stripe size (how much data to write to one OST
+ before moving to the next OST).</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--directory</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Lists entries about a specified directory instead of its
+ contents (in the same manner as
+ <literal>ls -d</literal>).</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--recursive</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Recurses into all sub-directories.</para>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>setstripe</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Create new files with a specific file layout (stripe
+ pattern) configuration.
+ <footnote>
+ <para>The file cannot exist prior to using
+ <literal>setstripe</literal>. A directory must exist prior to
+ using
+ <literal>setstripe</literal>.</para>
+ </footnote></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <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.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--size stripe_size</literal>
+ <footnote>
+ <para>The default stripe-size is 0. The default start-ost is
+ -1. Do NOT confuse them! If you set start-ost to 0, all new
+ file creations occur on OST 0 (seldom a good idea).</para>
+ </footnote> </para>
+ </entry>
+ <entry>
+ <para>Number of bytes to store on an OST before moving to the
+ next OST. A stripe_size of 0 uses the file system's default
+ stripe size, (default is 1 MB). Can be specified with
+ <emphasis role="bold">k</emphasis>(KB),
+ <emphasis role="bold">m</emphasis>(MB), or
+ <emphasis role="bold">g</emphasis>(GB), respectively.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--stripe-index start_ost_index</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>The OST index (base 10, starting at 0) on which to start
+ striping for this file. A start_ost_index value of -1 allows
+ the MDS to choose the starting index. This is the default
+ value, and it means that the MDS selects the starting OST as it
+ wants. We strongly recommend selecting this default, as it
+ allows space and load balancing to be done by the MDS as
+ needed. The
+ <literal>start_ost_index</literal> value has no relevance on
+ whether the MDS will use round-robin or QoS weighted allocation
+ for the remaining stripes in the file.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>
+ <literal>--ost-index ost_indices</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>This option is used to specify the exact stripe
+ layout on the the file system. <literal>ost_indices</literal>
+ is a list of OSTs referenced by their indices and index ranges
+ separated by commas, e.g. <literal>1,2-4,7</literal>.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> </para>
+ </entry>
+ <entry>
+ <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>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>setstripe -d</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Deletes default striping on the specified
+ directory.</para>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>pool_list {filesystem}[.poolname]|{pathname}</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Lists pools in the file system or pathname, or OSTs in
+ the file system's pool.</para>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>quota [-q] [-v] [-o
+ <replaceable>obd_uuid</replaceable>|-i
+ <replaceable>mdt_idx</replaceable>|-I
+ <replaceable>ost_idx</replaceable>] [-u|-g|-p
+ <replaceable>uname|uid|gname|gid|projid]</replaceable>
+ <replaceable>/mount_point</replaceable></literal>
+ </para>
+ <para> </para>
+ </entry>
+ <entry>
+ <para>Displays disk usage and limits, either for the full file
+ system or for objects on a specific OBD. A user or group name
+ or an usr, group and project ID can be specified. If all user,
+ group project ID are omitted, quotas for the current UID/GID
+ are shown. The <literal>-q</literal> option disables printing
+ of additional descriptions (including column titles). It fills
+ in blank spaces in the
+ <literal>grace</literal> column with zeros (when there is no
+ grace period set), to ensure that the number of columns is
+ consistent. The
+ <literal>-v</literal> option provides more verbose (per-OBD
+ statistics) output.</para>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>quota -t
+ <replaceable>-u|-g|-p</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>) or project (
+ <literal>-p</literal>) quotas.</para>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>quotachown</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Changes the file's owner and group on OSTs of the
+ specified file system.</para>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <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>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <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>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <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>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <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>
+ <caution>
+ <para>Use extreme caution when using this command; its
+ results cannot be undone.</para>
+ </caution>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>setquota {-u|-g|-p
+ <replaceable>uname|uid|gname|gid|projid}</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, groups or one project.
+ 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 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 -u|-g|-p [--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 '
+ <literal>XXwXXdXXhXXmXXs</literal>' format or as an integer
+ seconds value. See
+ <xref linkend="dbdoclet.50438206_11903" />.</para>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>help</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Provides brief help on various
+ <literal>lfs</literal> arguments.</para>
+ </entry>
+ </row>
+ <row>
+ <entry nameend="c2" namest="c1">
+ <para>
+ <literal>exit/quit</literal>
+ </para>
+ </entry>
+ <entry>
+ <para>Quits the interactive
+ <literal>lfs</literal> session.</para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </section>
+ <section remap="h5" xml:id="dbdoclet.50438206_11903">
+ <title>Examples</title>
+ <para>Creates a file striped on two OSTs with 128 KB on each
+ stripe.</para>
+ <screen>
+$ lfs setstripe -s 128k -c 2 /mnt/lustre/file1
+</screen>
+ <para>Deletes a default stripe pattern on a given directory. New files
+ use the default striping pattern.</para>
+ <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>
+ <screen>
+$ lfs find /mnt/lustre -mtime +30 -type f -print
+</screen>
+ <para>Recursively lists all files in a given directory that have objects
+ on OST2-UUID. The lfs check servers command checks the status of all
+ servers (MDT and OSTs).</para>
+ <screen>
+$ lfs find --obd OST2-UUID /mnt/lustre/
+</screen>
+ <para>Lists all OSTs in the file system.</para>
+ <screen>
+$ lfs osts
+</screen>
+ <para>Lists space usage per OST and MDT in human-readable format.</para>
+ <screen>
+$ lfs df -h
+</screen>
+ <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
+<replaceable>filesystem</replaceable>[.
+<replaceable>pool</replaceable>] |
+<replaceable>pathname</replaceable>
+</screen>
+ <para>List quotas of user 'bob'.</para>
+ <screen>
+$ lfs quota -u bob /mnt/lustre
+</screen>
+ <para>List quotas of project ID '1'.</para>
+ <screen>
+$ lfs quota -p 1 /mnt/lustre
+</screen>
+ <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>
+ <para>Checks quotas for user and group. Turns on quotas after making the
+ check.</para>
+ <screen>
+$ lfs quotacheck -ug /mnt/lustre
+</screen>
+ <para>Turns on quotas of user and group.</para>
+ <screen>
+$ lfs quotaon -ug /mnt/lustre
+</screen>
+ <para>Turns off quotas of user and group.</para>
+ <screen>
+$ lfs quotaoff -ug /mnt/lustre
+</screen>
+ <para>Sets quotas of user 'bob', with a 1 GB block quota hardlimit and a
+ 2 GB block quota softlimit.</para>
+ <screen>
+$ lfs setquota -u bob --block-softlimit 2000000 --block-hardlimit 1000000
+/mnt/lustre
+</screen>
+ <para>Sets grace times for user quotas: 1000 seconds for block quotas, 1
+ week and 4 days for inode quotas.</para>
+ <screen>
+$ lfs setquota -t -u --block-grace 1000 --inode-grace 1w4d /mnt/lustre
+</screen>
+ <para>Checks the status of all servers (MDT, OST)</para>
+ <screen>
+$ lfs check servers
+</screen>
+ <para>Creates a file striped on two OSTs from the pool
+ <literal>my_pool</literal></para>
+ <screen>
+$ lfs setstripe --pool my_pool -c 2 /mnt/lustre/file
+</screen>
+ <para>Lists the pools defined for the mounted Lustre file system
+ <literal>/mnt/lustre</literal></para>
+ <screen>
+$ lfs pool_list /mnt/lustre/
+</screen>
+ <para>Lists the OSTs which are members of the pool
+ <literal>my_pool</literal> in file system
+ <literal>my_fs</literal></para>
+ <screen>
+$ lfs pool_list my_fs.my_pool
+</screen>
+ <para>Finds all directories/files associated with
+ <literal>poolA</literal>.</para>
+ <screen>
+$ lfs find /mnt/lustre --pool poolA
+</screen>
+ <para>Finds all directories/files not associated with a pool.</para>
+ <screen>
+$ lfs find /mnt//lustre --pool ""
+</screen>
+ <para>Finds all directories/files associated with pool.</para>
+ <screen>
+$ lfs find /mnt/lustre ! --pool ""
+</screen>
+ <para>Associates a directory with the pool
+ <literal>my_pool</literal>, so all new files and directories are created
+ in the pool.</para>
+ <screen>
+$ lfs setstripe --pool my_pool /mnt/lustre/dir
+</screen>
+ </section>
+ <section remap="h5">
+ <title>See Also</title>
+ <para>
+ <xref linkend="dbdoclet.50438219_38274" />
+ </para>
+ </section>
+ </section>
+ <section xml:id="dbdoclet.lfs_migrate">
+ <title>
+ <indexterm>
+ <primary>lfs_migrate</primary>
+ </indexterm>
+ <literal>lfs_migrate</literal>
+ </title>
+ <para>The
+ <literal>lfs_migrate</literal> utility is a simple to migrate file
+ <emphasis>data</emphasis> between OSTs.</para>
+ <section remap="h5">
+ <title>Synopsis</title>
+ <screen>
+lfs_migrate [<replaceable>lfs_setstripe_options</replaceable>]
+ [-h] [-n] [-q] [-R] [-s] [-y] [-0] [file|directory ...]
+</screen>