linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: <linux-btrfs@vger.kernel.org>, <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests/btrfs: do not test btrfs/010 with autodefrag
Date: Fri, 27 Sep 2013 09:45:44 -0400	[thread overview]
Message-ID: <20130927134544.GI18681@localhost.localdomain> (raw)
In-Reply-To: <1379481475-10842-1-git-send-email-bo.li.liu@oracle.com>

On Wed, Sep 18, 2013 at 01:17:55PM +0800, Liu Bo wrote:
> btrfs/010 is going to create a fragmented file, however, with autodefrag
> this is impossible, so just skip the test when we're with autodefrag.
> 
> Signed-off-by: Liu Bo <bo.li.liu@oracle.com>

I'd rather you just strip out the autodefrag option if it is there and add it
back once the test is done (or hell just remove it, mount, and add it back).
Thanks,

Josef

  reply	other threads:[~2013-09-27 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18  5:17 [PATCH] xfstests/btrfs: do not test btrfs/010 with autodefrag Liu Bo
2013-09-27 13:45 ` Josef Bacik [this message]
2013-10-01 14:40   ` David Sterba

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=20130927134544.GI18681@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=bo.li.liu@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=xfs@oss.sgi.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).