Lustre 1.6 Operations Manual

3. Determine the obdfilter instance names on all clients. The names appear as the
4th column of lctl dl. For example:
$ pdsh -w oss[01-02] lctl dl |grep obdfilter |sort
oss01: 0 UP obdfilter oss01-sdb oss01-sdb_UUID 3
oss01: 2 UP obdfilter oss01-sdd oss01-sdd_UUID 3
oss02: 0 UP obdfilter oss02-sdi oss02-sdi_UUID 3
Here the obdfilter instance names are oss01-sdb, oss01-sdd, oss02-sdi.
Since you are driving obdfilter instances directly, set the shell array variable,
ost_names, to the names of the obdfilter instances and leave the client_names
variable undefined. For example:
ost_names_str='oss01:oss01-sdb oss01:oss01-sdd oss02:oss02-sdi'\
./obdfilter-survey
19.2.2.2 Running obdfilter_survey Against a Network
If you are driving obdfilter or obdecho instances over the network, then you must
instantiate the echo_clients. Set the shell array variable client_names to the
names of the echo_client instances and leave the ost_names variable undefined.
Optionally, you can prefix any name in ost_names or client_names with the
hostname that it runs on, for example, remote_node:ost4. If you are running
remote nodes, make sure these requirements are met:
■ The custom_remote_shell() works on your cluster.
■
■
All pathnames that you specify in the script are mounted on the node from which
obdfilter_survey is started and on all remote nodes.
The obdfilter_survey script is installed on clients at the same location as the
master node.
To run the obdfilter_survey script against a network:
1. Bring up obdecho instances on the servers and echo_client instances on the
clients, and run the included echo.sh on a node that has Lustre installed. Shell
variables:
■ SERVERS: Set this to a list of server hostnames or hostname of the current node
is used. This may be the wrong interface, so be sure to check it.
Note – echo.sh could probably be smarter about this.
19-6 Lustre 1.6 Operations Manual • September 2008