public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Chandra Seetharaman <sekharan@us.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	XFS Mailing List <xfs@oss.sgi.com>
Subject: Re: Failure of xfstests test case 202
Date: Sat, 11 Jun 2011 17:07:00 +1000	[thread overview]
Message-ID: <20110611070700.GB32466@dastard> (raw)
In-Reply-To: <1307741624.7661.453.camel@chandra-lucid.beaverton.ibm.com>

On Fri, Jun 10, 2011 at 02:33:44PM -0700, Chandra Seetharaman wrote:
> 
> On Fri, 2011-06-10 at 17:19 -0400, Christoph Hellwig wrote:
> > On Fri, Jun 10, 2011 at 01:39:47PM -0700, Chandra Seetharaman wrote:
> > > Hi all,
> > > 
> > > Test case 202 tries to create a single AG filesystem and runs xfs_repair
> > > on it expecting it to fail.
> > > 
> > > But, when I run the test with a filesystem that is bigger than 1TB it
> > > fails (not pleasantly) since the max AG size is 1TB.
> > > 
> > > I am thinking of the following solution, please let me know if there is
> > > any other elegant fix.
> > 
> > What about:
> > 
> > #
> > # The AG size is limited to 1TB (or even less with historic xfsprogs),
> > # so chose a small enough filesystem to make sure we can actually create
> > # a single AG filesystem.
> > #
> > _scratch_mkfs_sized `expr 1024 \* 1024 \* 1024`
> > 
> > instead?
> 
> Good point. Here is a solution based on your suggestion, but not using
> _scratch_mkfs_sized (sincein the current context we need it to take
> extra option, whereas _scratch_mkfs_sized takes fixed options).
> 
> What do you think ?
> 
> ----------------
> diff --git a/202 b/202
> index cbdcb57..b982956 100755
> --- a/202
> +++ b/202
> @@ -41,11 +41,18 @@ _supported_os Linux
>  
>  _require_scratch
>  
> +#
> +# The AG size is limited to 1TB (or even less with historic xfsprogs),
> +# so chose a small enough filesystem to make sure we can actually create
> +# a single AG filesystem.
> +#
>  echo "== Creating single-AG filesystem =="
> -_scratch_mkfs_xfs -d agcount=1 >/dev/null 2>&1
> +_scratch_mkfs_xfs -d agcount=1 -d size=$((1024*1024*1024)) >/dev/null 2>&1 \
> + || _fail "!!! failed to make filesystem with single AG"

Should work for most test setups.

>  
>  echo "== Trying to repair it (should fail) =="
> -_scratch_xfs_repair
> +_scratch_xfs_repair \
> + && _fail "!!! xfs_repair of single AG filesystem succeeded. Expected to fail."

But as I said before, this change is not necessary.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-06-11  7:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-10 20:39 Failure of xfstests test case 202 Chandra Seetharaman
2011-06-10 21:19 ` Christoph Hellwig
2011-06-10 21:33   ` Chandra Seetharaman
2011-06-11  7:07     ` Dave Chinner [this message]
2011-06-10 21:41 ` Dave Chinner
2011-06-10 23:25   ` Chandra Seetharaman
2011-06-11  6:59     ` Dave Chinner

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=20110611070700.GB32466@dastard \
    --to=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=sekharan@us.ibm.com \
    --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