linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: david@fromorbit.com, darrick.wong@oracle.com
Cc: linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org,
	fstests@vger.kernel.org, xfs@oss.sgi.com
Subject: [PATCH v4 00/11] xfstests: test the nfs/cifs/btrfs/xfs reflink/dedupe ioctls
Date: Sat, 19 Dec 2015 01:10:52 -0800	[thread overview]
Message-ID: <20151219091052.15320.94973.stgit@birch.djwong.org> (raw)

Hi all,

This is a small patch set against the reflink/dedupe test cases in
xfstests.  The first patch is a rewrite of the tools to find the
lowest vacant ID number and to move a test case.  These two programs
are useful for staging a lot of new tests at a high number and moving
them to lower numbers when the maintainer wants to accept the new
tests.

The second patch fixes some reflink tests that didn't clean up after
themselves.

Patch 3 updates the golden output for the test that examines the
results of feeding bad inputs to the two ioctls.  The new error values
are based on a discussion of how to react to bad file types on the
mailing lists and the ongoing work to hoist the ioctls to the VFS
level.

Patches 4-5 fix some minor errors found while testing with different
kernel config and block size options.

Patch 6 introduces new tests to check the behavior of unaligned CoW,
punch-while-CoWd, and ensures that passing len == 0 to reflink
actually runs to EOF.

Patch 7 introduces some XFS-specific ENOSPC testing, wherein we try to
crash the filesystem by allocating all the blocks in an AG and then
expanding the refcount and rmap btrees until the AG runs out of space.

Patch 8 introduces checks that CoW works with a variety of different
neighbor blocks -- delalloc, unwritten, hole, and regular.

Patch 9 introduces checks for CoW when blocksize < pagesize.

Patch 10 tries some large CoW operations to ensure that it works
correctly.

Patch 11 creates a 'dedupe' group for testing specifically dedupe
functionality.

If you're going to start using this mess, you probably ought to just
pull from my github trees for kernel[1], xfsprogs[2], xfstests[3],
xfs-docs[4], and man-pages[5].  They should just work with the btrfs
that's in 4.4...  and somewhat buggily with the 4.4 XFS patched with
[1].  The relevant xfs_io support will be in xfsprogs 4.3 though it
still needs a patch to fix len == 0 support.  Probably easier just to
grab [2] and build that.

Comments and questions are, as always, welcome.

--D

[1] https://github.com/djwong/linux/tree/for-dave
[2] https://github.com/djwong/xfsprogs/tree/for-dave
[3] https://github.com/djwong/xfstests/tree/for-dave
[4] https://github.com/djwong/xfs-documentation/tree/for-dave
[5] https://github.com/djwong/man-pages/commits/for-mtk

             reply	other threads:[~2015-12-19  9:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19  9:10 Darrick J. Wong [this message]
2015-12-19  9:10 ` [PATCH 01/11] test-scripts: test migration scripts Darrick J. Wong
2015-12-19  9:11 ` [PATCH 02/11] tests: don't leave cruft behind on the TEST_MNT Darrick J. Wong
2015-12-19  9:11 ` [PATCH 03/11] generic/15[78]: fix error messages in the golden output Darrick J. Wong
2015-12-19  9:11 ` [PATCH 04/11] xfs/128: allow larger margin for disk space usage Darrick J. Wong
2015-12-19  9:11 ` [PATCH 05/11] xfs/129: require loop Darrick J. Wong
2015-12-19  9:11 ` [PATCH 06/11] reflink: more tests Darrick J. Wong
2015-12-21  6:31   ` Dave Chinner
2016-01-04 19:47     ` Darrick J. Wong
2015-12-19  9:11 ` [PATCH 07/11] reflink: test ENOSPC when expanding btrees during reflink operations Darrick J. Wong
2015-12-19  9:11 ` [PATCH 08/11] reflink: more CoW tests for reflink and dedupe Darrick J. Wong
2015-12-19  9:11 ` [PATCH 09/11] reflink: test CoW with blocksize < pagesize Darrick J. Wong
2015-12-19  9:12 ` [PATCH 10/11] reflink: test a big CoW operation Darrick J. Wong
2015-12-19  9:12 ` [PATCH 11/11] generic: create a dedupe group Darrick J. Wong

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=20151219091052.15320.94973.stgit@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).