From: Zorro Lang <zlang@redhat.com>
To: fstests@vger.kernel.org
Subject: [PATCH] shared/010: avoid dedupe testing blocked on large fs
Date: Wed, 12 Sep 2018 18:15:47 +0800 [thread overview]
Message-ID: <20180912101547.28835-1-zlang@redhat.com> (raw)
When test on large fs (--large-fs), xfstests preallocates a large
file in SCRATCH_MNT/ at first. Duperemove will take too long time
to deal with that large file (many days on 500T XFS). So move
working directory to a sub-dir underlying $SCRATCH_MNT/.
Signed-off-by: Zorro Lang <zlang@redhat.com>
---
Hi,
Besides fix this issue, this patch fix another issue passingly. I left
a bad variable named "testdir" in this case. This patch can fix it.
If maintainer feels I should fix it in another patch, please tell me:-P
Thanks,
Zorro
tests/shared/010 | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/tests/shared/010 b/tests/shared/010
index 1817081b..04f55890 100755
--- a/tests/shared/010
+++ b/tests/shared/010
@@ -65,15 +65,17 @@ function end_test()
sleep_time=$((50 * TIME_FACTOR))
# Start fsstress
+testdir="$SCRATCH_MNT/dir"
+mkdir $testdir
fsstress_opts="-r -n 1000 -p $((5 * LOAD_FACTOR))"
-$FSSTRESS_PROG $fsstress_opts -d $SCRATCH_MNT -l 0 >> $seqres.full 2>&1 &
+$FSSTRESS_PROG $fsstress_opts -d $testdir -l 0 >> $seqres.full 2>&1 &
dedup_pids=""
dupe_run=$TEST_DIR/${seq}-running
# Start several dedupe processes on same directory
touch $dupe_run
for ((i = 0; i < $((2 * LOAD_FACTOR)); i++)); do
while [ -e $dupe_run ]; do
- $DUPEREMOVE_PROG -dr --dedupe-options=same $SCRATCH_MNT/ \
+ $DUPEREMOVE_PROG -dr --dedupe-options=same $testdir \
>>$seqres.full 2>&1
done &
dedup_pids="$! $dedup_pids"
--
2.14.4
next reply other threads:[~2018-09-12 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 10:15 Zorro Lang [this message]
2018-09-13 16:28 ` [PATCH] shared/010: avoid dedupe testing blocked on large fs Eric Sandeen
2018-09-14 1:10 ` Zorro Lang
2018-09-13 23:01 ` Dave Chinner
2018-09-14 1:13 ` Zorro Lang
2018-09-14 22:01 ` Dave Chinner
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=20180912101547.28835-1-zlang@redhat.com \
--to=zlang@redhat.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