From: Omar Sandoval <osandov@fb.com>
To: <fstests@vger.kernel.org>
Cc: <linux-btrfs@vger.kernel.org>,
Wang Yanfeng <wangyf-fnst@cn.fujitsu.com>,
Omar Sandoval <osandov@fb.com>
Subject: [PATCH 0/3] xfstests: test btrfs replace on RAID 5/6
Date: Thu, 23 Jul 2015 13:51:48 -0700 [thread overview]
Message-ID: <cover.1437683940.git.osandov@fb.com> (raw)
Btrfs has supported replace on RAID 5 and 6 since 3.19, but xfstests
hasn't been updated to reflect that. Patches 1 and 2 in this series fix
that.
Additionally, I'm including Wang Yanfeng's test for my patch series
"Btrfs: RAID 5/6 missing device scrub+replace", updated to use the
infrastructure added by patch 2.
Thanks!
Omar Sandoval (2):
btrfs/011: test replace on RAID 5/6 now that it's supported
btrfs: add replace missing and replace RAID 5/6 to profile configs
Wang Yanfeng (1):
btrfs: add a test of replace missing dev in diff raid
common/rc | 96 +++++++++++++++++++++++++++--------------------------
tests/btrfs/011 | 4 +--
tests/btrfs/095 | 93 +++++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/095.out | 2 ++
tests/btrfs/group | 1 +
5 files changed, 147 insertions(+), 49 deletions(-)
create mode 100755 tests/btrfs/095
create mode 100644 tests/btrfs/095.out
--
2.4.6
next reply other threads:[~2015-07-23 20:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 20:51 Omar Sandoval [this message]
2015-07-23 20:51 ` [PATCH 1/3] btrfs/011: test replace on RAID 5/6 now that it's supported Omar Sandoval
2015-07-24 3:01 ` Eryu Guan
2015-07-24 12:10 ` David Sterba
2015-07-23 20:51 ` [PATCH 2/3] btrfs: add replace missing and replace RAID 5/6 to profile configs Omar Sandoval
2015-07-24 3:03 ` Eryu Guan
2015-07-24 12:09 ` David Sterba
2015-07-24 17:50 ` Omar Sandoval
2015-07-27 22:22 ` Brendan Hide
2015-07-27 22:44 ` Hugo Mills
2015-07-28 16:52 ` David Sterba
2015-07-28 17:41 ` Omar Sandoval
2015-07-23 20:51 ` [PATCH 3/3] btrfs: add a test of replace missing dev in diff raid Omar Sandoval
2015-07-24 3:28 ` Eryu Guan
2015-07-24 17:52 ` Omar Sandoval
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=cover.1437683940.git.osandov@fb.com \
--to=osandov@fb.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangyf-fnst@cn.fujitsu.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).