23.07.2014 Views

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The sgpdd_survey script must be customized according to the particular device<br />

being tested and also according to the location where it should keep its working<br />

files. Customization variables are described explicitly at the start of the script.<br />

When the sgpdd_survey script runs, it creates a number of working files and a pair<br />

of result files. All files start with the prefix given by the script variable ${rslt}.<br />

${rslt}_.summary same as stdout<br />

${rslt}__* tmp files<br />

${rslt}_.detail collected tmp files for post-mortem<br />

The summary file and stdout should contain lines like this:<br />

total_size 8388608K rsz 1024 thr 1 crg 1 180.45 MB/s 1 x 180.50 \<br />

=/ 180.50 MB/s<br />

The number immediately before the first MB/s is bandwidth, computed by<br />

measuring total data and elapsed time. The remaining numbers are a check on the<br />

bandwidths reported by the individual sgp_dd instances.<br />

If there are so many threads that the sgp_dd script is unlikely to be able to allocate<br />

I/O buffers, then "ENOMEM" is printed.<br />

If one or more sgp_dd instances do not successfully report a bandwidth number,<br />

then "failed" is printed.<br />

19.2.2 obdfilter_survey<br />

The obdfilter_survey script processes sequential I/O with varying numbers of<br />

threads and objects (files) by using lctl::test_brw to drive the echo_client<br />

connected to local or remote obdfilter instances, or remote obdecho instances. It can<br />

be used to characterize the performance of the following <strong>Lustre</strong> components:<br />

Stripe F/S<br />

Here, the script directly exercises one or more instances of obdfilter. The script may<br />

be running on one or more nodes, for example, when the nodes are all attached to<br />

the same multi-ported disk subsystem.<br />

You need to tell the script the names of all obdfilter instances, which should already<br />

be up and running. If some instances are on different nodes, then you also need to<br />

specify their hostnames, for example, node1:ost1. All the obdfilter instances are<br />

driven directly. The script automatically loads the obdecho module (if required) and<br />

creates one instance of echo_client for each obdfilter instance.<br />

19-4 <strong>Lustre</strong> <strong>1.6</strong> <strong>Operations</strong> <strong>Manual</strong> • September 2008

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!