LU-3129 osd: Get FID from LMA if not in directory entry

[fs/lustre-release.git] / lustre / tests / README

diff --git a/lustre/tests/README b/lustre/tests/README
index 2e50b8a..00634a7 100644 (file)
--- a/lustre/tests/README
+++ b/lustre/tests/README
@@ -3,7 +3,7 @@ The various .xml configs in the tests/ directory are built by running the
 corresponding .sh script.  The .sh script runs a series of lmc (Lustre make
 config) commands in order to build up an XML file.  It is much easier to
 simply edit a .sh script and rebuild your XML config file than trying to
-edit the XML directly.  For example, the above configurations are:
+edit the XML directly.
 
 For a loopback setup with a mounted filesystem, you could do something like:
 
@@ -30,11 +30,10 @@ This configuration could be run on any 3 systems with the following commands:
     system3# ../utils/lconf --node uml3 uml.xml
 
 The "--node <name>" parameter tells lconf to use the configuration for
-the node "name" in the XML configuration file.  The internals of lconf
-and portals handle the configuration details for setting up netowrking.
-
-A variety of tests can be run or environments set up.  The most common way
-to build XML configuration
+the node "name" in the XML configuration file.  If the hostnames were
+already "uml1", "uml2", and "uml3", then the "--node" parameter would
+not need to be given.  The internals of lconf and portals handle the
+configuration details for setting up netowrking.
 
 2. runregression-net.sh and runregression-brw.sh
 
@@ -52,12 +51,13 @@ You can create a simple echo client by running the "llecho.sh" to
 run the tests locally (over TCP loopback), or edit llecho.sh to
 specify the SERVER and CLIENT names.  You would then set up as normal:
 
-    # for a single system, or for a remote server
+    # if you are using a remote server, first run:
     server# ../utils/lconf echo.xml
 
-Launch the test script via:
+Configure the client (or if you are running a single system only):
 
-    client# sh runregression-net.sh echo.xml
+    client# ../utils/lconf echo.xml
+    client# sh runregression-net.sh
 
 3. runtests
 
@@ -79,4 +79,7 @@ can just use runtests directly.  If this is only a client machine, the
     sh runtests [--reformat] <conf>.xml
 
 This creates a few simple files and directories first, and then untars
-a copy of the /etc filesystem into the Lustre filesystem.
+a copy of the /etc filesystem into the Lustre filesystem.  It then does
+data verification both before and after the filesystem is remounted, and
+finally deletes all of the files and verifies that the amount of space
+left in the filesystem is (nearly) the same as it was before the test.