From: Dave Chinner <david@fromorbit.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] shared/010: avoid dedupe testing blocked on large fs
Date: Fri, 14 Sep 2018 09:01:21 +1000 [thread overview]
Message-ID: <20180913230121.GB16550@dastard> (raw)
In-Reply-To: <20180912101547.28835-1-zlang@redhat.com>
On Wed, Sep 12, 2018 at 06:15:47PM +0800, Zorro Lang wrote:
> 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"
Can we not call a temporary on the scratch device "testdir"?
Because the "test dir" name specifically refers to the test device
mount point, and using it for anything else (even though it's a
different variable) is just confusing.
Call it something like "local_dir" or "work_dir" or "stress_dir".
But not "testdir".
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-09-14 4:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 10:15 [PATCH] shared/010: avoid dedupe testing blocked on large fs Zorro Lang
2018-09-13 16:28 ` Eric Sandeen
2018-09-14 1:10 ` Zorro Lang
2018-09-13 23:01 ` Dave Chinner [this message]
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=20180913230121.GB16550@dastard \
--to=david@fromorbit.com \
--cc=fstests@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