public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: Dave Chinner <david@fromorbit.com>
Cc: fstests@vger.kernel.org, Joao Eduardo Luis <joao@suse.de>
Subject: Re: [PATCH] common: add CephFS support
Date: Thu, 3 Nov 2016 12:49:45 +0100	[thread overview]
Message-ID: <20161103124945.04536a62@suse.de> (raw)
In-Reply-To: <20161102221755.GH14023@dastard>

On Thu, 3 Nov 2016 09:17:55 +1100, Dave Chinner wrote:

> On Wed, Nov 02, 2016 at 10:00:54AM +0100, David Disseldorp wrote:
> > From: Joao Eduardo Luis <joao@suse.de>
> > 
> > Add basic CephFS support. No new CephFS specific tests are included,
> > just basic enablement, with ./check now accepting a -ceph parameter.  
> 
> We don't add command line parameters to specify the filesystem
> anymore if we can avoid it (they are legacy options, really).
> Specifying FSTYP=ceph in the environment or config file should be
> sufficient to do they right thing - does this work for ceph?

Yes, seems to work okay for me.

> 
> > @@ -1499,6 +1508,15 @@ _require_scratch_nocheck()
> >  			_notrun "this test requires a valid \$SCRATCH_MNT"
> >  		fi
> >  		;;
> > +        ceph)
> > +		echo $SCRATCH_DEV | grep -q ":/" > /dev/null 2>&1
> > +		if [ -z "$SCRATCH_DEV" -o "$?" != "0" ]; then
> > +			_notrun "this test requires a valid \$SCRATCH_DEV"
> > +		fi
> > +		if [ ! -d "$SCRATCH_MNT" ]; then
> > +			_notrun "this test requires a valid \$SCRATCH_MNT"
> > +		fi
> > +		;;  
> 
> This is the same check as for nfs*). Can you make those common?

Sure, will fix and resend. Thanks for the feedback Dave.

Cheers, David

      reply	other threads:[~2016-11-03 11:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02  9:00 [PATCH] common: add CephFS support David Disseldorp
2016-11-02 22:17 ` Dave Chinner
2016-11-03 11:49   ` David Disseldorp [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=20161103124945.04536a62@suse.de \
    --to=ddiss@suse.de \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=joao@suse.de \
    /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