From: Omar Sandoval <osandov@osandov.com>
To: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com, Omar Sandoval <osandov@fb.com>
Subject: [PATCH v2 0/2] fstests: btrfs: the lost levels
Date: Thu, 28 Apr 2016 10:33:35 -0700 [thread overview]
Message-ID: <cover.1461864695.git.osandov@fb.com> (raw)
From: Omar Sandoval <osandov@fb.com>
Changes since v1:
- Fixed _supported_fs and _supported_os in patch 2
- Added Josef's Reviewed-by
Original cover letter below:
Inspired by a conversation a few of us had at LSF about forgotten
fstests, I went back and checked if I had let any tests disappear into
the ether. Turns out that I did, so here are the tests for Btrfs replace
missing that I never got merged, updated with everyone's comments from
last time around ([1], [2]). Patch 1/3 in that original series did get
merged but the last two didn't fare so well.
Thanks!
1: https://patchwork.kernel.org/patch/6856101/
2: https://patchwork.kernel.org/patch/6856051/
Omar Sandoval (2):
btrfs: add replace missing and replace RAID 5/6 to profile configs
btrfs: add test for replacing a missing device
common/rc | 95 ++++++++++++++++++++---------------------
tests/btrfs/027 | 119 ++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/027.out | 2 +
tests/btrfs/group | 1 +
4 files changed, 170 insertions(+), 47 deletions(-)
create mode 100755 tests/btrfs/027
create mode 100644 tests/btrfs/027.out
--
2.8.0
next reply other threads:[~2016-04-28 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 17:33 Omar Sandoval [this message]
2016-04-28 17:33 ` [PATCH v2 1/2] btrfs: add replace missing and replace RAID 5/6 to profile configs Omar Sandoval
2016-04-28 17:33 ` [PATCH v2 2/2] btrfs: add test for replacing a missing device 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.1461864695.git.osandov@fb.com \
--to=osandov@osandov.com \
--cc=fstests@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@fb.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).