From: Darrick J. Wong <djwong@xxxxxxxxxx>
For online fsck stress testing, increase the number of filesystem
operations per fsstress run to 2 million, now that we have the ability
to kill fsstress if the user should push ^C to abort the test early.
This should guarantee a couple of hours of continuous stress testing in
between clearing the scratch filesystem.
Signed-off-by: Darrick J. Wong <djwong@xxxxxxxxxx>
---
common/fuzzy | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/common/fuzzy b/common/fuzzy
index 01cf7f00d8..3e23edc9e4 100644
--- a/common/fuzzy
+++ b/common/fuzzy
@@ -399,7 +399,9 @@ __stress_scrub_fsstress_loop() {
local end="$1"
local runningfile="$2"
- local args=$(_scale_fsstress_args -p 4 -d $SCRATCH_MNT -n 2000 $FSSTRESS_AVOID)
+ # As of March 2022, 2 million fsstress ops should be enough to keep
+ # any filesystem busy for a couple of hours.
+ local args=$(_scale_fsstress_args -p 4 -d $SCRATCH_MNT -n 2000000 $FSSTRESS_AVOID)
echo "Running $FSSTRESS_PROG $args" >> $seqres.full
while __stress_scrub_running "$end" "$runningfile"; do
