From: Gao Xiang <hsiangkao@redhat.com>
To: Eryu Guan <guan@eryu.me>
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org,
"Darrick J. Wong" <djwong@kernel.org>,
Zorro Lang <zlang@redhat.com>
Subject: Re: [RFC PATCH v3 3/3] xfs: stress test for shrinking free space in the last AG
Date: Mon, 29 Mar 2021 04:09:12 +0800 [thread overview]
Message-ID: <20210328200912.GC3213575@xiangao.remote.csb> (raw)
In-Reply-To: <YGCy5W+4coMuM7y1@desktop>
On Mon, Mar 29, 2021 at 12:46:29AM +0800, Eryu Guan wrote:
> On Mon, Mar 15, 2021 at 07:19:26PM +0800, Gao Xiang wrote:
> > This adds a stress testcase to shrink free space as much as
> > possible in the last AG with background fsstress workload.
> >
> > The expectation is that no crash happens with expected output.
> >
> > Signed-off-by: Gao Xiang <hsiangkao@redhat.com>
> > ---
> > tests/xfs/991 | 122 ++++++++++++++++++++++++++++++++++++++++++++++
> > tests/xfs/991.out | 8 +++
> > tests/xfs/group | 1 +
> > 3 files changed, 131 insertions(+)
> > create mode 100755 tests/xfs/991
> > create mode 100644 tests/xfs/991.out
> >
> > diff --git a/tests/xfs/991 b/tests/xfs/991
> > new file mode 100755
> > index 00000000..7e7d318e
> > --- /dev/null
> > +++ b/tests/xfs/991
> > @@ -0,0 +1,122 @@
> > +#! /bin/bash
> > +# SPDX-License-Identifier: GPL-2.0
> > +# Copyright (c) 2020-2021 Red Hat, Inc. All Rights Reserved.
> > +#
> > +# FS QA Test 991
> > +#
> > +# XFS online shrinkfs stress test
> > +#
> > +# This test attempts to shrink unused space as much as possible with
> > +# background fsstress workload. It will decrease the shrink size if
> > +# larger size fails. And totally repeat 2 * TIME_FACTOR times.
> > +#
> > +seq=`basename $0`
> > +seqres=$RESULT_DIR/$seq
> > +echo "QA output created by $seq"
> > +
> > +here=`pwd`
> > +tmp=/tmp/$$
> > +status=1 # failure is the default!
> > +trap "rm -f $tmp.*; exit \$status" 0 1 2 3 15
> > +
> > +# get standard environment, filters and checks
> > +. ./common/rc
> > +. ./common/filter
> > +
> > +create_scratch()
> > +{
> > + _scratch_mkfs_xfs $@ | tee -a $seqres.full | \
> > + _filter_mkfs 2>$tmp.mkfs >/dev/null
> > + . $tmp.mkfs
> > +
> > + if ! _try_scratch_mount 2>/dev/null; then
> > + echo "failed to mount $SCRATCH_DEV"
> > + exit 1
> > + fi
>
> _scratch_mount will do the check and _fail the test on mount failure.
It was just copied & pasted from somewhere else rather than wrote from
scratch.
>
> > +
> > + # fix the reserve block pool to a known size so that the enospc
> > + # calculations work out correctly.
> > + _scratch_resvblks 1024 > /dev/null 2>&1
> > +}
> > +
> > +fill_scratch()
> > +{
> > + $XFS_IO_PROG -f -c "falloc -k 0 $1" $SCRATCH_MNT/resvfile
> > +}
> > +
> > +stress_scratch()
> > +{
> > + procs=3
> > + nops=$((1000 * LOAD_FACTOR))
>
> Declare procs and nops as local.
Will update, thanks for the suggestion.
>
> > + # -w ensures that the only ops are ones which cause write I/O
> > + FSSTRESS_ARGS=`_scale_fsstress_args -d $SCRATCH_MNT -w -p $procs \
> > + -n $nops $FSSTRESS_AVOID`
> > + $FSSTRESS_PROG $FSSTRESS_ARGS >> $seqres.full 2>&1 &
>
> I think it's more explicit to run run stress_scratch in background,
> instead run fsstress in background implicit.
Will update as well.
>
> > +}
> > +
> > +# real QA test starts here
> > +_supported_fs xfs
>
> _require_scratch
No, _require_xfs_shrink also checks this.
>
> > +_require_xfs_shrink
> > +_require_xfs_io_command "falloc"
> > +
> > +rm -f $seqres.full
> > +_scratch_mkfs_xfs | tee -a $seqres.full | _filter_mkfs 2>$tmp.mkfs
> > +. $tmp.mkfs # extract blocksize and data size for scratch device
> > +
> > +decsize=`expr 42 \* 1048576` # shrink in chunks of this size at most
> > +endsize=`expr 125 \* 1048576` # stop after shrinking this big
> > +[ `expr $endsize / $dbsize` -lt $dblocks ] || _notrun "Scratch device too small"
> > +
> > +nags=2
> > +totalcount=$((2 * TIME_FACTOR))
> > +
> > +while [ $totalcount -gt 0 ]; do
> > + size=`expr 1010 \* 1048576` # 1010 megabytes initially
> > + logblks=$(_scratch_find_xfs_min_logblocks -dsize=${size} -dagcount=${nags})
> > +
> > + create_scratch -lsize=${logblks}b -dsize=${size} -dagcount=${nags}
> > +
> > + for i in `seq 125 -1 90`; do
> > + fillsize=`expr $i \* 1048576`
> > + out="$(fill_scratch $fillsize 2>&1)"
> > + echo "$out" | grep -q 'No space left on device' && continue
> > + test -n "${out}" && echo "$out"
> > + break
> > + done
> > +
> > + while [ $size -gt $endsize ]; do
> > + stress_scratch
>
> So just call
>
> stress_scratch &
>
> here? So it's clear that we put stress_scratch in background, and the
> 'wait' below is waiting for it.
Will update.
Thanks,
Gao Xiang
>
> Thanks,
> Eryu
>
> > + sleep 1
> > +
> > + decb=`expr $decsize / $dbsize` # in data blocks
> > + while [ $decb -gt 0 ]; do
> > + sizeb=`expr $size / $dbsize - $decb`
> > +
> > + $XFS_GROWFS_PROG -D ${sizeb} $SCRATCH_MNT \
> > + >> $seqres.full 2>&1 && break
> > +
> > + [ $decb -gt 100 ] && decb=`expr $decb + $RANDOM % 10`
> > + decb=`expr $decb / 2`
> > + done
> > +
> > + wait
> > + [ $decb -eq 0 ] && break
> > +
> > + # get latest dblocks
> > + $XFS_INFO_PROG $SCRATCH_MNT 2>&1 | _filter_mkfs 2>$tmp.growfs >/dev/null
> > + . $tmp.growfs
> > +
> > + size=`expr $dblocks \* $dbsize`
> > + _scratch_unmount
> > + _repair_scratch_fs >> $seqres.full
> > + _scratch_mount
> > + done
> > +
> > + _scratch_unmount
> > + _repair_scratch_fs >> $seqres.full
> > + totalcount=`expr $totalcount - 1`
> > +done
> > +
> > +echo "*** done"
> > +status=0
> > +exit
> > diff --git a/tests/xfs/991.out b/tests/xfs/991.out
> > new file mode 100644
> > index 00000000..e8209672
> > --- /dev/null
> > +++ b/tests/xfs/991.out
> > @@ -0,0 +1,8 @@
> > +QA output created by 991
> > +meta-data=DDEV isize=XXX agcount=N, agsize=XXX blks
> > +data = bsize=XXX blocks=XXX, imaxpct=PCT
> > + = sunit=XXX swidth=XXX, unwritten=X
> > +naming =VERN bsize=XXX
> > +log =LDEV bsize=XXX blocks=XXX
> > +realtime =RDEV extsz=XXX blocks=XXX, rtextents=XXX
> > +*** done
> > diff --git a/tests/xfs/group b/tests/xfs/group
> > index a7981b67..cf190b59 100644
> > --- a/tests/xfs/group
> > +++ b/tests/xfs/group
> > @@ -526,3 +526,4 @@
> > 526 auto quick mkfs
> > 527 auto quick quota
> > 990 auto quick growfs
> > +991 auto growfs ioctl prealloc stress
> > --
> > 2.27.0
>
prev parent reply other threads:[~2021-03-28 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 11:19 [RFC PATCH v3 0/3] xfs: testcases for shrinking free space in the last AG Gao Xiang
2021-03-15 11:19 ` [RFC PATCH v3 1/3] common/xfs: add a _require_xfs_shrink helper Gao Xiang
2021-03-28 16:18 ` Eryu Guan
2021-03-28 19:51 ` Gao Xiang
2021-03-15 11:19 ` [RFC PATCH v3 2/3] xfs: basic functionality test for shrinking free space in the last AG Gao Xiang
2021-03-28 16:32 ` Eryu Guan
2021-03-28 20:06 ` Gao Xiang
2021-03-29 2:14 ` Eryu Guan
2021-03-29 2:43 ` Gao Xiang
2021-03-15 11:19 ` [RFC PATCH v3 3/3] xfs: stress " Gao Xiang
2021-03-28 16:46 ` Eryu Guan
2021-03-28 20:09 ` Gao Xiang [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=20210328200912.GC3213575@xiangao.remote.csb \
--to=hsiangkao@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.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).