generic: hole punching followed by writes in the same range

[xfstests-dev.git] / README

diff --git a/README b/README
index f788e7187930fed42009fad6daae0d70f0912a69..fd491e4a86b055085839f84ca99525c71f5ae0d1 100644 (file)
--- a/README
+++ b/README
@@ -15,7 +15,7 @@ Building Linux:
                gawk gcc indent libtool lvm2 make psmisc quota sed \
                xfsdump xfsprogs \
                libacl-devel libattr-devel libaio-devel libuuid-devel \
-               openssl-devel xfsprogs-devel btrfs-progs-devel
+               xfsprogs-devel btrfs-progs-devel
                (Older distributions may require xfsprogs-qa-devel as well.)
                (Note that for RHEL and CentOS, you may need the EPEL repo.)
        - run make
@@ -117,16 +117,18 @@ Running tests:
     - By default the tests suite will run xfs tests:
     - ./check '*/001' '*/002' '*/003'
     - ./check '*/06?'
-    - You can explicitly specify NFS/CIFS/UDF, otherwise the filesystem type will
-      be autodetected from $TEST_DEV:
-      ./check -nfs [test(s)]
     - Groups of tests maybe ran by: ./check -g [group(s)]
       See the 'group' file for details on groups
-    - for udf tests: ./check -udf [test(s)]
-      Running all the udf tests: ./check -udf -g udf
-    - for running nfs tests: ./check -nfs [test(s)]
-    - for running cifs/smb3 tests: ./check -cifs [test(s)]
     - To randomize test order: ./check -r [test(s)]
+    - You can explicitly specify NFS/CIFS/UDF/OVERLAY, otherwise
+      the filesystem type will be autodetected from $TEST_DEV:
+        - for running nfs tests: ./check -nfs [test(s)]
+        - for running cifs/smb3 tests: ./check -cifs [test(s)]
+        - for udf tests: ./check -udf [test(s)]
+          Running all the udf tests: ./check -udf -g udf
+        - for overlay tests: ./check -overlay [test(s)]
+          The TEST and SCRATCH partitions should be pre-formatted
+          with another base fs, where the overlay dirs will be created
 
     
     The check script tests the return value of each script, and
@@ -272,6 +274,9 @@ Pass/failure:
     The elapsed time for the most recent pass for each test is kept
     in "check.time".
 
+    The compare-failures script in tools/ may be used to compare failures
+    across multiple runs, given files containing stdout from those runs.
+
 __________________
 SUBMITTING PATCHES
 __________________