generic: hole punching followed by writes in the same range

[xfstests-dev.git] / README

diff --git a/README b/README
index 3cac4b35268513cc8051aa7743b3a81a3ddd81a4..fd491e4a86b055085839f84ca99525c71f5ae0d1 100644 (file)
--- a/README
+++ b/README
@@ -6,15 +6,16 @@ Building Linux:
        - cd into the xfstests directory
        - install prerequisite packages
          For example, for Ubuntu:
-               "sudo apt-get install xfslibs-dev uuid-dev libtool-bin e2fsprogs
-                automake gcc libuuid1 quota attr libattr1-dev make
-                libacl1-dev libaio-dev xfsprogs libgdbm-dev gawk fio dbench
-                uuid-runtime"
+               sudo apt-get install xfslibs-dev uuid-dev libtool-bin \
+               e2fsprogs automake gcc libuuid1 quota attr libattr1-dev make \
+               libacl1-dev libaio-dev xfsprogs libgdbm-dev gawk fio dbench \
+               uuid-runtime
          For Fedora, RHEL, or CentOS:
-               "yum install acl attr awk bc dbench dump e2fsprogs fio gawk
-                indent lvm2 psmisc quota sed xfsdump xfsprogs
-                libacl-devel libattr-devel libaio-devel libuuid-devel
-                openssl-devel xfsprogs-devel btrfs-progs-devel"
+               yum install acl attr automake bc dbench dump e2fsprogs fio \
+               gawk gcc indent libtool lvm2 make psmisc quota sed \
+               xfsdump xfsprogs \
+               libacl-devel libattr-devel libaio-devel libuuid-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
@@ -62,7 +63,7 @@ Preparing system for tests (IRIX and Linux):
               
     - setup your environment
        Quick start:
-       - copy config.local.example to config.local and edit as needed
+       - copy local.config.example to local.config and edit as needed
        Or:
         - setenv TEST_DEV "device containing TEST PARTITION"
         - setenv TEST_DIR "mount point of TEST PARTITION"   
@@ -116,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
@@ -270,3 +273,12 @@ Pass/failure:
     The recent pass/fail history is maintained in the file "check.log".
     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
+__________________
+
+Send patches to the fstests mailing list at fstests@vger.kernel.org.