xmlns:xi="http://www.w3.org/2001/XInclude" xml:id="userutilities">
<title xml:id="userutilities.title">User Utilities</title>
<para>This chapter describes user utilities.</para>
- <section xml:id="dbdoclet.50438206_94597">
+ <section xml:id="userutilities.lfs">
<title>
<indexterm>
<primary>lfs</primary>
guarantee that
<literal>atime</literal> is kept coherent across the
cluster.)</para>
- <para>OSTs store a transient
+ <para>OSTs by default only hold 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
+ <literal>atime</literal> is written to the MDT 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>mdd.*.atime_diff</literal>).
+ </para>
+ <para condition='l2D'>In Lustre 2.14, it is possible to set
+ the OSTs to persistently store atime with each object, in
+ order to get more accurate persistent atime updates for files
+ that are open for a long time via the similarly-named
+ <literal>obdfilter.*.atime_diff</literal> parameter.
+ </para>
+ <para>
+ The client considers the latest <literal>atime</literal> from
+ all OSTs and MDTs. If a
<literal>setattr</literal> is set by user, then it is updated on
- both the MDS and OST, allowing the
+ both the MDT and OST, allowing the
<literal>atime</literal> to go backward.</para>
</entry>
</row>
</entry>
<entry>
<para>Name of the pre-defined pool of OSTs (see
- <xref linkend="dbdoclet.50438219_38274" />) that will be used
+ <xref linkend="lctl" />) that will be used
for striping. The
<literal>stripe_cnt</literal>,
<literal>stripe_size</literal> and
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>
+ <xref linkend="setquota_grace_time_example" />.</para>
</entry>
</row>
<row>
groups. Grace time is specified in '
<literal>XXwXXdXXhXXmXXs</literal>' format or as an integer
seconds value. See
- <xref linkend="dbdoclet.50438206_11903" />.</para>
+ <xref linkend="setquota_grace_time_example" />.</para>
</entry>
</row>
<row>
</tgroup>
</informaltable>
</section>
- <section remap="h5" xml:id="dbdoclet.50438206_11903">
+ <section remap="h5" xml:id="setquota_grace_time_example">
<title>Examples</title>
<para>Creates a file striped on two OSTs with 128 KB on each
stripe.</para>
<section remap="h5">
<title>See Also</title>
<para>
- <xref linkend="dbdoclet.50438219_38274" />
+ <xref linkend="lctl" />
</para>
</section>
</section>
- <section xml:id="dbdoclet.lfs_migrate">
+ <section xml:id="lfs_migrate">
<title>
<indexterm>
<primary>lfs_migrate</primary>
reduced fragmentation. The tool
<literal>filefrag</literal> can be used to report file fragmentation.
See
- <xref linkend="dbdoclet.50438206_75125" /></para>
+ <xref linkend="filefrag" /></para>
</note>
<note>
<para>As long as a file has extent lengths of tens of megabytes (
<section remap="h5">
<title>See Also</title>
<para>
- <xref linkend="dbdoclet.50438206_94597" />
+ <xref linkend="userutilities.lfs" />
</para>
</section>
</section>
- <section xml:id="dbdoclet.50438206_75125">
+ <section xml:id="filefrag">
<title>
<indexterm>
<primary>filefrag</primary>
</screen>
</section>
</section>
- <section xml:id="dbdoclet.50438206_86244">
+ <section xml:id="mount">
<title>
<indexterm>
<primary>mount</primary>
</tgroup>
</informaltable>
</section>
- <section xml:id="dbdoclet.50438206_56217">
+ <section xml:id="handling_timeouts">
<title>Handling Timeouts</title>
<para>Timeouts are the most common cause of hung applications. After a
timeout involving an MDS or failover OST, applications attempting to access