From: bxue@redhat.com
To: fstests@vger.kernel.org
Cc: Boyang Xue <bxue@redhat.com>
Subject: [PATCH v1] generic/476: requires 27GB scratch size
Date: Thu, 21 Jul 2022 10:29:59 +0800 [thread overview]
Message-ID: <20220721022959.4189726-1-bxue@redhat.com> (raw)
From: Boyang Xue <bxue@redhat.com>
The test requires larger scratch dev size when running on top of NFS other
than ext4 and xfs. It requires at least 27GB in my test. Without this
requirement, the test run never finishes on NFS, leaving 100% scratch disk
space use.
Signed-off-by: Boyang Xue <bxue@redhat.com>
---
Hi,
I find generic/476 easily goes into an infinite run on top of NFS. When it
happens, the common pattern is 100% disk space use of SCRATCH_MNT, and
`nfsiostat` shows 50% write error on SCRATCH_MNT. When I run it with a large
enough SCRATCH_MNT, the problem disappears. So I post this patch to add the size
requirement.
Please help review this patch. Thanks!
-Boyang
tests/generic/476 | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/generic/476 b/tests/generic/476
index 212373d1..dcc7c3da 100755
--- a/tests/generic/476
+++ b/tests/generic/476
@@ -24,6 +24,7 @@ _cleanup()
_supported_fs generic
_require_scratch
+_require_scratch_size $((27 * 1024 * 1024)) # 27GB
_require_command "$KILLALL_PROG" "killall"
echo "Silence is golden."
--
2.27.0
next reply other threads:[~2022-07-21 2:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 2:29 bxue [this message]
2022-07-21 2:49 ` [PATCH v1] generic/476: requires 27GB scratch size xuyang2018.jy
2022-07-21 7:17 ` Boyang Xue
2022-07-21 4:40 ` Darrick J. Wong
2022-07-21 7:26 ` Boyang Xue
2022-07-21 11:42 ` Theodore Ts'o
2022-07-21 14:03 ` Theodore Ts'o
2022-07-21 15:12 ` Chuck Lever III
2022-07-21 15:14 ` Chuck Lever III
2022-07-21 18:04 ` Theodore Ts'o
2022-07-21 18:13 ` Chuck Lever III
2022-07-22 2:18 ` Theodore Ts'o
2022-08-04 9:10 ` Boyang Xue
2022-07-21 15:29 ` Zorro Lang
2022-07-21 15:32 ` Chuck Lever III
2022-07-21 16:30 ` Zorro Lang
2022-07-21 18:25 ` Jeff Layton
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=20220721022959.4189726-1-bxue@redhat.com \
--to=bxue@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