public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Ronnie Sahlberg <lsahlber@redhat.com>
To: fstests <fstests@vger.kernel.org>
Cc: Steve French <smfrench@gmail.com>
Subject: [PATCH] cifs: Add README.cifs
Date: Tue, 22 May 2018 08:52:47 +1000	[thread overview]
Message-ID: <20180521225247.17811-1-lsahlber@redhat.com> (raw)

This is a patch to provide quickstart instructions for how to use xfstest
for CIFS.

Signed-off-by: Ronnie Sahlberg <lsahlber@redhat.com>
---
 README.cifs | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 61 insertions(+)
 create mode 100644 README.cifs

diff --git a/README.cifs b/README.cifs
new file mode 100644
index 00000000..92efd24d
--- /dev/null
+++ b/README.cifs
@@ -0,0 +1,61 @@
+This describes how to get up and running using xfstests for the CIFS filesystem.
+
+There are additional information on testing cifs with xfstest on the samba
+wiki : https://wiki.samba.org/index.php/Xfstesting-cifs
+
+
+
+Quick Setup
+===========
+
+local.config
+------------
+Xfstests needs two cifs shares. One normal share and one scratch share.
+The data on the scratch share will be destroyed so set this up as a dedicate
+share on your server and do not store anything important in it.
+
+The first thing we need is to set up some stanzas for different smb dialects.
+These dialects can then be selected using the -s command line option making
+it a convenient way to pick a specific version of smb to test.
+
+Download the example configuration and name it local.config:
+
+  wget https://wiki.samba.org/images/9/99/Xfstests.local.config.txt \
+      -O local.config
+
+Update local.config and change SERVER, SHARE, SCRATCH, USERNAME, PASSWORD to
+match your shares.
+
+Create the /mnt/test and /mnt/share mountpoints.
+
+
+Exclusion files
+---------------
+Some tests do not yet work for SMB and some tests take very long so we may want
+to skip them. In CIFS we do this using exclusion files.
+
+Download the exclusion files for smb3 and for very slow tests:
+
+  wget https://wiki.samba.org/images/9/99/Xfstests.exclude.very-slow.txt \
+      -O tests/cifs/exclude.very-slow
+  wget https://wiki.samba.org/images/d/d9/Xfstests.exclude.known-broken-smb3.txt
+      -O tests/cifs/exclude.known-broken-smb3
+
+
+Running full set of tests
+=========================
+With some luck you should be ready to run your first xfstest now.
+
+When runnig the "full" set of tests there are multiple tests that are
+known to fail. Reasons can be that they just don't map well to cifs,
+we are missing features in cifs or there are bugs that needs to be fixed.
+
+For regression testing is useful to run all the tests that are known to work.
+We can acheive this per protocol version using exclude files and filter
+out the known broken tests.
+
+SMB3
+----
+
+    sudo ./check -s smb3 -E tests/cifs/exclude.known-broken-smb3 \
+        -E tests/cifs/exclude.very-slow
-- 
2.13.3


             reply	other threads:[~2018-05-21 22:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 22:52 Ronnie Sahlberg [this message]
2018-05-22  2:36 ` [PATCH] cifs: Add README.cifs Eryu Guan
2018-05-22  5:12 ` Dave Chinner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180521225247.17811-1-lsahlber@redhat.com \
    --to=lsahlber@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=smfrench@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox