From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: david@fromorbit.com, darrick.wong@oracle.com
Cc: linux-ext4@vger.kernel.org, fstests@vger.kernel.org,
linux-btrfs@vger.kernel.org, xfs@oss.sgi.com
Subject: [RFC 00/11] xfstests: test the btrfs/xfs reflink/dedupe ioctls
Date: Mon, 29 Jun 2015 21:15:20 -0700 [thread overview]
Message-ID: <20150630041519.2476.23059.stgit@birch.djwong.org> (raw)
Hi all,
This is a RFC-quality pass at making xfstests perform more rigorous
testing of the btrfs/xfs file clone, reflink, and dedupe ioctls.
There are now tests of the basic functionality of the three ioctls;
tests to ensure that the filesystem exhibits the expected copy on
write semantics; tests to try to suss out race conditions in the new
write paths; tests to ensure that the ioctls peform basic disk
accounting correctly; tests of the interaction between reflink and the
various fallocate verbs (allocate, punch, collapse, insert zeroes);
and some attempts to test the upper limits of reflinking. The first
patch in the series adds fuzz testing to ext4 and XFS; aside from
being first in line, it isn't tied to any of the reflink
functionality.
To run these tests, you'll have to patch xfsprogs to have reflink and
dedupe support[1]; the patch ought to apply fairly cleanly against the
upstream git. They should more or less work with the btrfs that
appears in 4.1, though if you want to test the XFS implementation,
you're going to have to apply a lot of patches to the kernel and
xfsprogs. See the cover letters[2][3] for those patchsets for more
information.
Known issues:
* I think the race checks for dedupe could be a little sharper at
finding mistakes.
* I started the numbering really high to prevent the tests from
colliding with whatever new tests might arrive; this will require
some intervention to fix.
* When ext4 gains reflink support, it shouldn't be difficult to make
these tests run on it. The patch set is based on the current
xfstest master on kernel.org.
* If the copy_file_range syscall ever comes around, we'll have to
adapt xfs_io to use that in addition to the btrfs ioctls.
Comments and questions are, as always, welcome.
--D
[1] http://djwong.org/docs/03-xfs_io-reflink-and-dedupe.patch
[2] See thread "[RFC 00/15] xfsprogs: support the reflink btree" dated today.
[3] http://oss.sgi.com/archives/xfs/2015-06/msg00407.html
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2015-06-30 4:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 4:15 Darrick J. Wong [this message]
2015-06-30 4:15 ` [PATCH 01/11] fuzz XFS and ext4 filesystems Darrick J. Wong
2015-06-30 4:15 ` [PATCH 02/11] move btrfs reflink tests to generic Darrick J. Wong
2015-06-30 4:15 ` [PATCH 03/11] generic/32[6-8]: support xfs in addition to btrfs Darrick J. Wong
2015-06-30 4:15 ` [PATCH 04/11] basic tests of the reflink and dedupe ioctls Darrick J. Wong
2015-06-30 4:15 ` [PATCH 05/11] test CoW behaviors of reflinked files Darrick J. Wong
2015-06-30 4:16 ` [PATCH 06/11] reflink fallocate tests Darrick J. Wong
2015-06-30 4:16 ` [PATCH 07/11] reflink concurrent operations tests Darrick J. Wong
2015-06-30 4:16 ` [PATCH 08/11] test reflink for accuracy in free block counts Darrick J. Wong
2015-06-30 4:16 ` [PATCH 09/11] test error conditions on reflink Darrick J. Wong
2015-06-30 4:16 ` [PATCH 10/11] test xfs-specific reflink pieces Darrick J. Wong
2015-06-30 4:16 ` [PATCH 11/11] reflink: test what happens when we hit resource limits 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=20150630041519.2476.23059.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).