linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Fasheh <mfasheh@suse.de>
To: Dave Chinner <david@fromorbit.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] fstests: btrfs: add test for quota groups and drop snapshot
Date: Thu, 1 Oct 2015 12:31:39 -0700	[thread overview]
Message-ID: <20151001193139.GA1044@wotan.suse.de> (raw)
In-Reply-To: <20150928232858.GA27164@dastard>

On Tue, Sep 29, 2015 at 09:28:58AM +1000, Dave Chinner wrote:
> On Wed, Sep 23, 2015 at 02:05:16PM -0700, Mark Fasheh wrote:
> > Since the last time I sent this test, drop snapshot was broken again with
> > respect to qgroups. What practical step could I take to get a test for that
> > in here which I can beat the btrfs developers over the head with the next
> > time someone handwaves this problem away ;)
> 
> I'll merge tests that break a filesystem as a reminder to developers
> that there is a problem that needs fixing. We do that from time to
> time for XFS issues that are either really hard to fix or not urgent
> but require significant amounts of work to correct...

That sounds like a good policy, thank you.


> > From: Mark Fasheh <mfasheh@suse.de>
> > 
> > [PATCH] btrfs: add test for quota groups and drop snapshot
> ....
> > +# NOTE: The ability to vary tree height for this test is very useful
> > +# for debugging problems with drop_snapshot(). As a result we retain
> > +# that parameter even though the test below always does level 2 trees.
> > +_explode_fs_tree () {
> > +	local level=$1;
> > +	local loc="$2";
> > +	local n;
> > +
> > +	if [ -z $loc ]; then
> > +	    echo "specify location for fileset"
> > +	    exit 1;
> > +	fi
> > +
> > +	case $level in
> > +	    1)# this always reproduces level 1 trees
> > +		n=10;
> > +		;;
> > +	    2)# this always reproduces level 2 trees
> > +		n=1500
> 
> Still some minor whitespace issues, but I can fix that on commit
> as everything else looks fine.

Erf, my bad I tried copying the style in some of the common/ dir but
obviously failed :(  Thanks for the review and help Dave, it is greatly
appreciated.
	--Mark

--
Mark Fasheh

      reply	other threads:[~2015-10-01 19:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 22:16 [PATCH] fstests: btrfs: add test for quota groups and drop snapshot Mark Fasheh
2015-09-23  2:47 ` Dave Chinner
2015-09-23 21:05   ` Mark Fasheh
2015-09-28 23:28     ` Dave Chinner
2015-10-01 19:31       ` Mark Fasheh [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=20151001193139.GA1044@wotan.suse.de \
    --to=mfasheh@suse.de \
    --cc=david@fromorbit.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).