linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: Dave Chinner <david@fromorbit.com>, Eryu Guan <eguan@redhat.com>
Cc: <fstests@vger.kernel.org>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v3 00/15] xfstests: new btrfs stress test cases
Date: Fri, 26 Sep 2014 08:56:30 -0400	[thread overview]
Message-ID: <5425627E.8000300@fb.com> (raw)
In-Reply-To: <20140925053907.GC4758@dastard>

On 09/25/2014 01:39 AM, Dave Chinner wrote:
> Btrfs developers,
>
> Can someone who knows how this is all supposed to work pass an eye
> over this patch series to determine the validity of what is being
> tested?  Given the number of problems this patchset seems to expose,
> it looks pretty important to me to get this into all of your regular
> testing. I can't make judgement on whether the tests are valid
> things to do to btrfs, so I'm reliant on people with actual btrfs
> expertise to vet these patches...
>

Yeah sorry Dave I've been meaning to get to this, I'll go through them 
all today.  Thanks,

Josef



  reply	other threads:[~2014-09-26 12:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18  5:49 [PATCH v3 00/15] xfstests: new btrfs stress test cases Eryu Guan
2014-09-18  5:49 ` [PATCH v3 01/15] btrfs: new test to run btrfs balance and subvolume test simultaneously Eryu Guan
2014-09-18  5:49 ` [PATCH v3 02/15] btrfs: new test to run btrfs balance and scrub simultaneously Eryu Guan
2014-09-18  5:49 ` [PATCH v3 03/15] btrfs: new test to run btrfs balance and defrag operations simultaneously Eryu Guan
2014-09-18  5:49 ` [PATCH v3 04/15] btrfs: new case to run btrfs balance and remount with different compress algorithms Eryu Guan
2014-09-18  5:49 ` [PATCH v3 05/15] btrfs: new case to run btrfs balance and device replace operations simultaneously Eryu Guan
2014-09-18  5:49 ` [PATCH v3 06/15] btrfs: new case to run btrfs subvolume create/delete operations and device replace simultaneously Eryu Guan
2014-09-18  5:49 ` [PATCH v3 07/15] btrfs: new case to run btrfs subvolume create/delete operations and scrub simultaneously Eryu Guan
2014-09-18  5:49 ` [PATCH v3 08/15] btrfs: new case to run btrfs subvolume create/delete and defrag operations simultaneously Eryu Guan
2014-09-18  5:49 ` [PATCH v3 09/15] btrfs: new case to run subvolume create/delete and remount with defferent compress algorithms Eryu Guan
2014-09-18  5:49 ` [PATCH v3 10/15] btrfs: new case to run device replace and scrub operations simultaneously Eryu Guan
2014-09-18  5:49 ` [PATCH v3 11/15] btrfs: new case to run device replace and defrag " Eryu Guan
2014-09-18  5:49 ` [PATCH v3 12/15] btrfs: new case to run device replace and remount with different compress algorithms simultaneously Eryu Guan
2014-09-18  5:49 ` [PATCH v3 13/15] btrfs: new case to run btrfs scrub and defrag operations simultaneously Eryu Guan
2014-09-18  5:49 ` [PATCH v3 14/15] btrfs: new case to run btrfs scrub and remount with different compress algorithms simultaneously Eryu Guan
2014-09-18  5:49 ` [PATCH v3 15/15] btrfs: new case to run defrag " Eryu Guan
2014-09-25  5:39 ` [PATCH v3 00/15] xfstests: new btrfs stress test cases Dave Chinner
2014-09-26 12:56   ` Josef Bacik [this message]
2014-09-26  3:55 ` Eryu Guan

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=5425627E.8000300@fb.com \
    --to=jbacik@fb.com \
    --cc=david@fromorbit.com \
    --cc=eguan@redhat.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).