linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: <dave@jikos.cz>
Cc: <xfs@oss.sgi.com>, <linux-fsdevel@vger.kernel.org>,
	Stefan Behrens <sbehrens@giantdisaster.de>,
	<linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] xfstests: make more tests generic
Date: Wed, 10 Aug 2011 11:36:09 -0500	[thread overview]
Message-ID: <1312994169.2865.41.camel@doink> (raw)
In-Reply-To: <20110810155214.GE20461@twin.jikos.cz>

On Wed, 2011-08-10 at 17:52 +0200, David Sterba wrote:
> Hi,
> 
> On Mon, Aug 01, 2011 at 12:31:19PM +0200, Stefan Behrens wrote:
> > Use _scratch_mkfs / _scratch_mkfs_sized instead of _scratch_mkfs_xfs
> > where possible.
> > Execute 015, 062, 083, 117, 120 and 192 for all filesystems, these
> > tests used to be XFS specific.
>  
> this patch is now in xfstests-dev and somehow breaks btrfs testing.

. . .

> there's a hardcoded path for mkfs.btrfs in common.rc:_scratch_mkfs_sized()
> 
> 335     btrfs)
> 336         /sbin/mkfs.$FSTYP $MKFS_OPTIONS $SCRATCH_DEV -b $fssize
> 337         ;;
> 
> I have a /usr/local/ installation of btrfsprogs from git,
> _scratch_mkfs_sized() was not called for btrfs before.
> 
> Possible ways to fix this:
> 1) use /sbin/mkfs -t $FSTYP like _scratch_mkfs, or
> 2) set $MKFS_BTRFS_PROG like for some other filesystems
> 
> 
> What is preferred?

Whatever works.  My personal preference would be option (1)
if it works, since it's does the generic thing directly
rather than suggesting something special is needed for
btrfs.  But if that doesn't work, consistency rules so
MKFS_BTRFS_PROG "like for some other filesystems" is good.

					-Alex


  parent reply	other threads:[~2011-08-10 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 10:31 [PATCH v3 0/2] xfstests: Changed a couple of tests to be generic Stefan Behrens
2011-08-01 10:31 ` [PATCH v3 1/2] xfstests: make more tests generic Stefan Behrens
2011-08-10 15:52   ` David Sterba
2011-08-10 16:33     ` Christoph Hellwig
2011-08-10 16:38       ` Alex Elder
2011-08-10 16:36     ` Alex Elder [this message]
2011-08-10 16:43       ` Christoph Hellwig
2011-08-01 10:31 ` [PATCH v3 2/2] xfstests: make t_immutable and 079 filesystem-agnostic Stefan Behrens
2011-08-01 11:03 ` [PATCH v3 0/2] xfstests: Changed a couple of tests to be generic Christoph Hellwig

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=1312994169.2865.41.camel@doink \
    --to=aelder@sgi.com \
    --cc=dave@jikos.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sbehrens@giantdisaster.de \
    --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).