Lustre 1.6 Operations Manual

NETS: set this if you are using a network type other than TCP.
For example:
■
SERVERS=oss01-eth2 sh echo.sh
2. On the servers, start the obdecho server and verify that it is up, run:
$ lctl dl
0 UP obdecho ost_oss01.local ost_oss01.local_UUID 3
1 UP ost OSS OSS_UUID 3
3. On the clients, start the other side of the echo connection, run:
$ lctl dl
0 UP osc OSC_xfer01.local_ost_oss01.local_ECHO_client \
6bc9b_ECHO_client_2a8a2cb3dd 5
1 UP echo_client ECHO_client 6bc9b_ECHO_client_2a8a2cb3dd 3
4. Verify connectivity from a client, run:
$ lctl ping SERVER_NID
5. Run the script on the master node, specifying the client names in an
environment variable. For example, run:
$ client_names_str='xfer01:ECHO_client xfer02:ECHO_client
xfer03:ECHO_client xfer04:ECHO_client xfer05:ECHO_client
xfer06:ECHO_client xfer07:ECHO_client xfer08:ECHO_client
xfer09:ECHO_client xfer10:ECHO_client xfer11:ECHO_client
xfer12:ECHO_client' ./obdfilter-survey
6. When aborting, run killall vmstat on clients:
pdsh -w (clients) killall vmstat
Use lctl device_list to verify the obdfilter/echo_client instance
names. For example, when the script runs, it creates a number of working files
and a pair of result files. All files start with the prefix given by ${rslt}.
${rslt}.summary
${rslt}.script_*
${rslt}.detail_tmp*
${rslt}.detail
same as stdout
per-host test script files
per-ost result files
collected result files for post-mortem
The script iterates over the given numbers of threads and objects performing all
specified tests and checking that all test processes completed successfully.
Note that the script does not clean up properly if it is aborted or if it encounters an
unrecoverable error. In this case, manual cleanup may be required, possibly
including killing any running instances of lctl (local or remote), removing
echo_client instances created by the script, and unloading obdecho.
Chapter 19 Lustre I/O Kit 19-7