From: Dave Chinner <david@fromorbit.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] xfstest: add tests/btrfs/059 to test seed operations
Date: Thu, 21 Aug 2014 09:08:38 +1000 [thread overview]
Message-ID: <20140820230838.GH26465@dastard> (raw)
In-Reply-To: <1408115781-4876-1-git-send-email-anand.jain@oracle.com>
On Fri, Aug 15, 2014 at 11:16:21PM +0800, Anand Jain wrote:
> This test contains a set of 5 sub test cases which will tests
> the device add and replacement on a seed FS. The kernel messages
> are checked at the end of the each of the 5 test cases to see
> if there are any kernel warnings or bugs reported. As in general
> btrfs do report warning when device counts such as num_devices
> and rw_devices appears to be wrong.
>
> Since the tests has to deal with the replace, it would need
> up to five scratch device with same size.
Please separate this out into 5 tests using shared infrastructure.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2014-08-20 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 15:16 [PATCH] xfstest: add tests/btrfs/059 to test seed operations Anand Jain
2014-08-20 23:08 ` Dave Chinner [this message]
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=20140820230838.GH26465@dastard \
--to=david@fromorbit.com \
--cc=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/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).