From: "Darrick J. Wong" <djwong@kernel.org>
To: Chandan Babu R <chandanrlinux@gmail.com>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org,
darrick.wong@oracle.com
Subject: Re: [PATCH V4 11/11] xfs: Stress test with bmap_alloc_minlen_extent error tag enabled
Date: Wed, 3 Mar 2021 10:12:02 -0800 [thread overview]
Message-ID: <20210303181202.GS7269@magnolia> (raw)
In-Reply-To: <20210118062022.15069-12-chandanrlinux@gmail.com>
On Mon, Jan 18, 2021 at 11:50:22AM +0530, Chandan Babu R wrote:
> This commit adds a stress test that executes fsstress with
> bmap_alloc_minlen_extent error tag enabled.
Haha, yikes.
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> Signed-off-by: Chandan Babu R <chandanrlinux@gmail.com>
> ---
> tests/xfs/531 | 84 +++++++++++++++++++++++++++++++++++++++++++++++
> tests/xfs/531.out | 7 ++++
> tests/xfs/group | 1 +
> 3 files changed, 92 insertions(+)
> create mode 100755 tests/xfs/531
> create mode 100644 tests/xfs/531.out
>
> diff --git a/tests/xfs/531 b/tests/xfs/531
> new file mode 100755
> index 00000000..fd92c3ea
> --- /dev/null
> +++ b/tests/xfs/531
> @@ -0,0 +1,84 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2020 Chandan Babu R. All Rights Reserved.
> +#
> +# FS QA Test 531
> +#
> +# Execute fsstress with bmap_alloc_minlen_extent error tag enabled.
> +#
> +seq=`basename $0`
> +seqres=$RESULT_DIR/$seq
> +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.*
> +}
> +
> +# get standard environment, filters and checks
> +. ./common/rc
> +. ./common/filter
> +. ./common/inject
> +. ./common/populate
> +
> +# remove previous $seqres.full before test
> +rm -f $seqres.full
> +
> +# real QA test starts here
> +
> +_supported_fs xfs
> +_require_scratch
> +_require_xfs_debug
> +_require_test_program "punch-alternating"
> +_require_xfs_io_error_injection "bmap_alloc_minlen_extent"
> +
> +echo "Format and mount fs"
> +_scratch_mkfs_sized $((1024 * 1024 * 1024)) >> $seqres.full
> +_scratch_mount >> $seqres.full
> +
> +bsize=$(_get_file_block_size $SCRATCH_MNT)
> +
> +echo "Consume free space"
> +fillerdir=$SCRATCH_MNT/fillerdir
> +nr_free_blks=$(stat -f -c '%f' $SCRATCH_MNT)
> +nr_free_blks=$((nr_free_blks * 90 / 100))
> +
> +_fill_fs $((bsize * nr_free_blks)) $fillerdir $bsize 0 >> $seqres.full 2>&1
> +
> +echo "Create fragmented filesystem"
> +for dentry in $(ls -1 $fillerdir/); do
> + $here/src/punch-alternating $fillerdir/$dentry >> $seqres.full
> +done
> +
> +echo "Inject bmap_alloc_minlen_extent error tag"
> +_scratch_inject_error bmap_alloc_minlen_extent 1
> +
> +echo "Scale fsstress args"
> +args=$(_scale_fsstress_args -p $((LOAD_FACTOR * 75)) -n $((TIME_FACTOR * 1000)))
> +
> +echo "Execute fsstress in background"
> +$FSSTRESS_PROG -d $SCRATCH_MNT $args \
> + -f bulkstat=0 \
> + -f bulkstat1=0 \
> + -f fiemap=0 \
> + -f getattr=0 \
> + -f getdents=0 \
> + -f getfattr=0 \
> + -f listfattr=0 \
> + -f mread=0 \
> + -f read=0 \
> + -f readlink=0 \
> + -f readv=0 \
> + -f stat=0 \
> + -f aread=0 \
> + -f dread=0 > /dev/null 2>&1
> +
> +# success, all done
> +status=0
> +exit
> diff --git a/tests/xfs/531.out b/tests/xfs/531.out
> new file mode 100644
> index 00000000..67f40654
> --- /dev/null
> +++ b/tests/xfs/531.out
> @@ -0,0 +1,7 @@
> +QA output created by 531
> +Format and mount fs
> +Consume free space
> +Create fragmented filesystem
> +Inject bmap_alloc_minlen_extent error tag
> +Scale fsstress args
> +Execute fsstress in background
> diff --git a/tests/xfs/group b/tests/xfs/group
> index 81a15582..f4cb5af6 100644
> --- a/tests/xfs/group
> +++ b/tests/xfs/group
> @@ -528,3 +528,4 @@
> 528 auto quick reflink
> 529 auto quick reflink
> 530 auto quick
> +531 auto stress
> --
> 2.29.2
>
prev parent reply other threads:[~2021-03-04 0:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 6:20 [PATCH V4 00/11] xfs: Tests to verify inode fork extent count overflow detection Chandan Babu R
2021-01-18 6:20 ` [PATCH V4 01/11] common/xfs: Add a helper to get an inode fork's extent count Chandan Babu R
2021-03-03 17:30 ` Darrick J. Wong
2021-03-05 14:41 ` Chandan Babu R
2021-01-18 6:20 ` [PATCH V4 02/11] xfs: Check for extent overflow when trivally adding a new extent Chandan Babu R
2021-03-03 17:38 ` Darrick J. Wong
2021-03-05 14:42 ` Chandan Babu R
2021-01-18 6:20 ` [PATCH V4 03/11] xfs: Check for extent overflow when growing realtime bitmap/summary inodes Chandan Babu R
2021-03-03 17:45 ` Darrick J. Wong
2021-03-04 11:58 ` Chandan Babu R
2021-03-04 16:17 ` Darrick J. Wong
2021-01-18 6:20 ` [PATCH V4 04/11] xfs: Check for extent overflow when punching a hole Chandan Babu R
2021-03-03 17:54 ` Darrick J. Wong
2021-01-18 6:20 ` [PATCH V4 05/11] xfs: Check for extent overflow when adding/removing xattrs Chandan Babu R
2021-03-03 17:56 ` Darrick J. Wong
2021-01-18 6:20 ` [PATCH V4 06/11] xfs: Check for extent overflow when adding/removing dir entries Chandan Babu R
2021-03-03 18:01 ` Darrick J. Wong
2021-03-04 12:22 ` Chandan Babu R
2021-01-18 6:20 ` [PATCH V4 07/11] xfs: Check for extent overflow when writing to unwritten extent Chandan Babu R
2021-03-03 18:05 ` Darrick J. Wong
2021-03-05 14:43 ` Chandan Babu R
2021-01-18 6:20 ` [PATCH V4 08/11] xfs: Check for extent overflow when moving extent from cow to data fork Chandan Babu R
2021-03-03 18:07 ` Darrick J. Wong
2021-01-18 6:20 ` [PATCH V4 09/11] xfs: Check for extent overflow when remapping an extent Chandan Babu R
2021-03-03 18:09 ` Darrick J. Wong
2021-01-18 6:20 ` [PATCH V4 10/11] xfs: Check for extent overflow when swapping extents Chandan Babu R
2021-03-03 18:10 ` Darrick J. Wong
2021-01-18 6:20 ` [PATCH V4 11/11] xfs: Stress test with bmap_alloc_minlen_extent error tag enabled Chandan Babu R
2021-03-03 18:12 ` Darrick J. Wong [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=20210303181202.GS7269@magnolia \
--to=djwong@kernel.org \
--cc=chandanrlinux@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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).