public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: Re: [patch] xfsqa test to check log size scaling
Date: Fri, 11 Jul 2008 08:45:15 +1000	[thread overview]
Message-ID: <20080710224515.GZ11558@disturbed> (raw)
In-Reply-To: <20080522061257.GR173056135@sgi.com>

ping?

On Thu, May 22, 2008 at 04:12:57PM +1000, David Chinner wrote:
> XFS-QA test to check that log size scaling works correctly
> for old and new maximum log sizes.
> 
> Signed-off-by: Dave Chinner <dgc@sgi.com>
> ---
>  xfstests/188     |   88 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  xfstests/188.out |   16 ++++++++++
>  xfstests/group   |    1 
>  3 files changed, 105 insertions(+)
> 
> Index: xfs-cmds/xfstests/188
> ===================================================================
> --- /dev/null	1970-01-01 00:00:00.000000000 +0000
> +++ xfs-cmds/xfstests/188	2008-05-15 22:39:08.741203552 +1000
> @@ -0,0 +1,88 @@
> +#! /bin/sh
> +# FS QA Test No. 188
> +#
> +# large log size mkfs test - ensure the log size scaling works
> +#
> +#-----------------------------------------------------------------------
> +# Copyright (c) 2008 Silicon Graphics, Inc.  All Rights Reserved.
> +#-----------------------------------------------------------------------
> +#
> +# creator
> +owner=dgc@sgi.com
> +
> +seq=`basename $0`
> +echo "QA output created by $seq"
> +
> +here=`pwd`
> +tmp=/tmp/$$
> +status=1	# failure is the default!
> +trap "_cleanup; exit \$status" 0 1 2 3 15
> +
> +_cleanup()
> +{
> +    cd /
> +    rm -f $tmp.*
> +    _cleanup_testdir
> +}
> +
> +# get standard environment, filters and checks
> +. ./common.rc
> +. ./common.filter
> +
> +# real QA test starts here
> +_supported_fs xfs
> +_supported_os Linux
> +
> +_setup_testdir
> +_require_scratch
> +_scratch_mkfs_xfs >/dev/null 2>&1
> +_scratch_mount
> +
> +_require_loop
> +LOOP_DEV=$SCRATCH_MNT/test_fs
> +LOOP_MNT=$SCRATCH_MNT/test_fs_dir
> +
> +_do_mkfs()
> +{
> +	for i in $*; do
> +		echo -n "fssize=${i}g "
> +		$MKFS_XFS_PROG -f -b size=4096 -l version=2 \
> +			-d name=$LOOP_DEV,size=${i}g |grep log
> +		mount -o loop -t xfs $LOOP_DEV $LOOP_MNT
> +		echo "test write" > $LOOP_MNT/test
> +		umount $LOOP_MNT
> +	done
> +}
> +# make large holey file
> +$XFS_IO_PROG -f -c "truncate 100t" $LOOP_DEV
> +
> +#make loopback mount dir
> +mkdir $LOOP_MNT
> +
> +# test if large logs are supported
> +LARGE_LOG=
> +$MKFS_XFS_PROG -f -l size=256m -d name=$LOOP_DEV,size=10g > /dev/null 2>&1
> +if [ $? -eq 0 ]; then
> +	LARGE_LOG=true
> +fi
> +
> +# walk over standard sizes (up to 256GB)
> +_do_mkfs 1 2 4 8 16 32 64 128 256
> +
> +if [ -n "$LARGE_LOG" ]; then
> +	# walk over larger sizes
> +	_do_mkfs 512 1024 2048 4096 8192 16384
> +else
> +	# just cut'n'paste from the golden output for the remaining sizes
> +	cat << EOF
> +fssize=512g log      =internal log           bsize=4096   blocks=65536, version=2
> +fssize=1024g log      =internal log           bsize=4096   blocks=131072, version=2
> +fssize=2048g log      =internal log           bsize=4096   blocks=262144, version=2
> +fssize=4096g log      =internal log           bsize=4096   blocks=521728, version=2
> +fssize=8192g log      =internal log           bsize=4096   blocks=521728, version=2
> +fssize=16384g log      =internal log           bsize=4096   blocks=521728, version=2
> +EOF
> +fi
> +
> +status=0
> +exit
> Index: xfs-cmds/xfstests/188.out
> ===================================================================
> --- /dev/null	1970-01-01 00:00:00.000000000 +0000
> +++ xfs-cmds/xfstests/188.out	2008-05-15 22:39:26.254922874 +1000
> @@ -0,0 +1,16 @@
> +QA output created by 188
> +fssize=1g log      =internal log           bsize=4096   blocks=2560, version=2
> +fssize=2g log      =internal log           bsize=4096   blocks=2560, version=2
> +fssize=4g log      =internal log           bsize=4096   blocks=2560, version=2
> +fssize=8g log      =internal log           bsize=4096   blocks=2560, version=2
> +fssize=16g log      =internal log           bsize=4096   blocks=2560, version=2
> +fssize=32g log      =internal log           bsize=4096   blocks=4096, version=2
> +fssize=64g log      =internal log           bsize=4096   blocks=8192, version=2
> +fssize=128g log      =internal log           bsize=4096   blocks=16384, version=2
> +fssize=256g log      =internal log           bsize=4096   blocks=32768, version=2
> +fssize=512g log      =internal log           bsize=4096   blocks=65536, version=2
> +fssize=1024g log      =internal log           bsize=4096   blocks=131072, version=2
> +fssize=2048g log      =internal log           bsize=4096   blocks=262144, version=2
> +fssize=4096g log      =internal log           bsize=4096   blocks=521728, version=2
> +fssize=8192g log      =internal log           bsize=4096   blocks=521728, version=2
> +fssize=16384g log      =internal log           bsize=4096   blocks=521728, version=2
> Index: xfs-cmds/xfstests/group
> ===================================================================
> --- xfs-cmds.orig/xfstests/group	2008-05-15 16:32:52.489519140 +1000
> +++ xfs-cmds/xfstests/group	2008-05-15 22:38:32.000000000 +1000
> @@ -275,3 +275,4 @@ filestreams	dgc@sgi.com
>  185 dmapi auto
>  186 attr auto
>  187 attr auto
> +188 log metadata auto
> 
> 

-- 
Dave Chinner
david@fromorbit.com

  parent reply	other threads:[~2008-07-10 22:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22  6:12 [patch] xfsqa test to check log size scaling David Chinner
2008-05-22 13:25 ` Christoph Hellwig
2008-05-22 22:12   ` David Chinner
2008-05-23  4:59     ` Christoph Hellwig
2008-07-10 22:45 ` Dave Chinner [this message]
2009-05-10 19:37 ` 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=20080710224515.GZ11558@disturbed \
    --to=david@fromorbit.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