Lustre 1.6 Operations Manual

Network
Here, the script drives one or more instances of obdecho via instances of
echo_client running on one or more nodes. You need to tell the script the names
of all echo_client instances, which should already be up and running. If some
instances are on different nodes, then you also need to specify their hostnames, for
example, node1:ECHO_node1.
Stripe F/S over the network
Here, the script drives one or more instances of obdfilter via instances of
echo_client running on one or more nodes. As noted above, you need to tell the
script the names of all echo_client instances, which should already be up and
running. Note that the script is not scalable to hundreds of nodes since it is only
intended to measure individual servers, not the scalability of the system as a whole.
Script
The script must be customized according to the components being tested and the
location where it should keep its working files. Customization variables are clearly
described at the beginning of the script.
19.2.2.1 Running obdfilter_survey Against a Local Disk
To run the obdfilter_survey script against a local disk:
1. Create a Lustre configuration shell script and XML, using your normal
methods. You do not need to specify an MDS or LOV, but you do need to list
all OSTs that you wish to test.
2. On all OSS machines, run:
$ mkfs.lustre --fsname spfs --mdt --mgs /dev/sda
Remember, write tests are destructive. This test should be run prior to startup of
your actual Lustre filesystem. If you do this, you will not need to reformat to
restart Lustre. However, if the test is terminated before completion, you may
have to remove objects from the disk.
Chapter 19 Lustre I/O Kit 19-5