From: Dave Chinner <david@fromorbit.com>
To: fstests@vger.kernel.org
Subject: [PATCH 2/5] fstests: remove old soak script
Date: Fri, 7 Mar 2025 08:34:47 +1100 [thread overview]
Message-ID: <20250306213921.3769440-3-david@fromorbit.com> (raw)
In-Reply-To: <20250306213921.3769440-1-david@fromorbit.com>
From: Dave Chinner <dchinner@redhat.com>
There is an old script for soak testing using check in the source
tree called "soak". All it does is run fsstress in a loop on the
scratch device, but to do that it needs to include the entire
fstests config/setup scripts.
These days we have much better soak testing capabilities (e.g. the
soak and stress groups, with controllable iterations, durations,
load, etc) so there's no point in keeping old scripts like this
around that add weird dependencies to the core infrastructure.
Remove it.
Signed-off-by: Dave Chinner <dchinner@redhat.com>
---
soak | 121 -----------------------------------------------------------
1 file changed, 121 deletions(-)
delete mode 100755 soak
diff --git a/soak b/soak
deleted file mode 100755
index d5c4229ad..000000000
--- a/soak
+++ /dev/null
@@ -1,121 +0,0 @@
-#!/bin/bash
-# SPDX-License-Identifier: GPL-2.0
-# Copyright (c) 2000-2002 Silicon Graphics, Inc. All Rights Reserved.
-#
-
-# get standard environment, filters and checks
-. ./common/rc
-. ./common/filter
-
-tmp=/tmp/$$
-seq=soak
-status=1 # failure is the default!
-
-_cleanup()
-{
- echo " *** umount"
- _scratch_unmount >/dev/null 2>&1
-}
-
-trap "_cleanup; exit \$status" 0 1 2 3 15
-
-ROOT="."
-LOG="$ROOT/soak.log"
-FULL="$ROOT/soak.full"
-
-_log()
-{
- echo "$*" 1>&2
- echo "$*" >>$LOG
- echo "$*" >>$FULL
-}
-
-_logp()
-{
- tee -a $FULL
-}
-
-_fail()
-{
- _log "$*"
- status=1
- exit 1
-}
-
-_require_scratch
-
-passes=-1
-stress=100000
-proc=1
-
-if [ $# -gt 0 ]
-then
- passes=$1
- if [ $# -gt 1 ]
- then
- stress=$2
- if [ $# -gt 2 ]
- then
- proc=$3
- fi
- fi
-fi
-
-echo "" >$FULL
-echo "" >$LOG
-_log "*** soak test started (passes=$passes, stress=$stress, proc=$proc)"
-_log "*** (`date`)"
-
-
-_log " *** init"
-_log " *** unmounting scratch device"
-
-_scratch_unmount 2>&1 >>$FULL
-
-_log " *** clean scratch device"
-
-mkfs_xfs -f $SCRATCH_DEV 2>&1 >>$FULL \
- || _fail " !!! failed to mkfs SCRATCH_DEV"
-
-pass=1
-
-while [ $pass -le $passes -o $passes -lt 0 ]
-do
- _log " *** pass $pass (`date`)"
-
- _log " *** check"
- _check_scratch_fs
-
- _log " *** mounting scratch device"
-
- if ! _scratch_mount 2>&1 | _logp
- then
- _fail " !!! failed to mount"
- fi
-
- if [ $pass != 1 ]
- then
- _log " *** cleanup"
- rm -rf $SCRATCH_MNT/soak_test \
- || _fail " !!! couldn't delete old dir"
-
- _log " *** check"
- _check_scratch_fs
- fi
-
- _log " *** mkdir"
- mkdir $SCRATCH_MNT/soak_test \
- || _fail " !!! couldn't delete old dir"
-
- _log " *** stress"
- ltp/fsstress -d $SCRATCH_MNT/soak_test -p $proc -n $stress $FSSTRESS_AVOID 2>&1 | \
- >>$FULL
-
- _log " *** unmounting scratch device"
-
- _scratch_unmount 2>&1 | _logp \
- || _fail " !!! failed to umount"
-
- let "pass = pass + 1"
-done
-
--
2.45.2
next prev parent reply other threads:[~2025-03-06 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 21:34 [PATCH 0/5] fstests: remove old SGI QE scripts Dave Chinner
2025-03-06 21:34 ` [PATCH 1/5] fstests: remove setup script Dave Chinner
2025-03-06 21:34 ` Dave Chinner [this message]
2025-03-06 21:34 ` [PATCH 3/5] fstests: remove crash script Dave Chinner
2025-03-06 21:34 ` [PATCH 4/5] fstests: remove tools/auto-qa Dave Chinner
2025-03-06 21:34 ` [PATCH 5/5] fstests: remove old tools from tools directory Dave Chinner
2025-03-06 22:59 ` [PATCH 0/5] fstests: remove old SGI QE scripts Darrick J. Wong
2025-03-07 4:04 ` David Disseldorp
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=20250306213921.3769440-3-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=fstests@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