</listitem>
<listitem>
<para><literal>ost-survey</literal> - Performs I/O against OSTs individually to allow
- performance comparisons to detect if an OST is performing suboptimally due to hardware
+ performance comparisons to detect if an OST is performing sub-optimally due to hardware
issues.</para>
</listitem>
</itemizedlist>
<para>Password-free remote access to nodes in the system (provided by <literal>ssh</literal> or <literal>rsh</literal>).</para>
</listitem>
<listitem>
- <para>LNET self-test completed to test that Lustre networking has been properly installed
+ <para>LNet self-test completed to test that Lustre networking has been properly installed
and configured. See <xref linkend="lnetselftest"/>.</para>
</listitem>
<listitem>
</listitem>
</itemizedlist>
<para>Download the Lustre I/O kit (<literal>lustre-iokit</literal>)from:</para>
- <para><link xl:href="http://downloads.hpdd.intel.com/">http://downloads.hpdd.intel.com/</link></para>
+ <para><link xl:href="http://downloads.whamcloud.com/">http://downloads.whamcloud.com/</link></para>
</section>
</section>
<section xml:id="dbdoclet.50438212_51053">
</listitem>
<listitem>
<para>On the server side, view the statistics at:</para>
- <screen>/proc/fs/lustre/obdecho/<replaceable>echo_srv</replaceable>/stats</screen>
+ <screen>lctl get_param obdecho.<replaceable>echo_srv</replaceable>.stats</screen>
<para>where <literal><replaceable>echo_srv</replaceable></literal>
is the <literal>obdecho</literal> server created by the script.</para>
</listitem>
</section>
<section remap="h4">
<title>Visualizing Results</title>
- <para>It is useful to import the <literal>obdfilter-survey</literal> script summary data (it
- is fixed width) into Excel (or any graphing package) and graph the bandwidth versus the
- number of threads for varying numbers of concurrent regions. This shows how the OSS
- performs for a given number of concurrently-accessed objects (files) with varying numbers
- of I/Os in flight.</para>
- <para>It is also useful to monitor and record average disk I/O sizes during each test using the 'disk io size' histogram in the file <literal>/proc/fs/lustre/obdfilter/</literal> (see <xref linkend="dbdoclet.50438271_55057"/> for details). These numbers help identify problems in the system when full-sized I/Os are not submitted to the underlying disk. This may be caused by problems in the device driver or Linux block layer.</para>
- <screen> */brw_stats</screen>
- <para>The <literal>plot-obdfilter</literal> script included in the I/O toolkit is an example of processing output files to a .csv format and plotting a graph using <literal>gnuplot</literal>.</para>
+ <para>It is useful to import the <literal>obdfilter-survey</literal>
+ script summary data (it is fixed width) into Excel (or any graphing
+ package) and graph the bandwidth versus the number of threads for
+ varying numbers of concurrent regions. This shows how the OSS performs
+ for a given number of concurrently-accessed objects (files) with varying
+ numbers of I/Os in flight.</para>
+ <para>It is also useful to monitor and record average disk I/O sizes
+ during each test using the 'disk io size' histogram in the
+ file <literal>lctl get_param obdfilter.*.brw_stats</literal>
+ (see <xref linkend="dbdoclet.50438271_55057"/> for details). These
+ numbers help identify problems in the system when full-sized I/Os are
+ not submitted to the underlying disk. This may be caused by problems in
+ the device driver or Linux block layer.</para>
+ <para>The <literal>plot-obdfilter</literal> script included in the I/O
+ toolkit is an example of processing output files to a .csv format and
+ plotting a graph using <literal>gnuplot</literal>.</para>
</section>
</section>
</section>