From: Eryu Guan <guan@eryu.me>
To: Sun Ke <sunke32@huawei.com>
Cc: fstests@vger.kernel.org, yuchao0@huawei.com
Subject: Re: [PATCH] generic/042: f2fs-utils 1.14.0 needs at least 52 MB
Date: Sun, 6 Jun 2021 22:07:04 +0800 [thread overview]
Message-ID: <YLzWiH5RwHFdEWIQ@desktop> (raw)
In-Reply-To: <20210601082005.1352814-1-sunke32@huawei.com>
On Tue, Jun 01, 2021 at 04:20:05AM -0400, Sun Ke wrote:
> f2fs-utils 1.9.0 needs at least 38 MB space for f2fs image. However,
> f2fs-utils 1.14.0 needs at least 52 MB. Not sure if it will change again.
> But at least we need to configure mininum size of f2fs image to 52MB now.
>
> Suggested-by: Chao Yu <yuchao0@huawei.com>
> Signed-off-by: Sun Ke <sunke32@huawei.com>
> ---
> tests/generic/042 | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/tests/generic/042 b/tests/generic/042
> index ee0e4b400c71..bf3b4180b1a2 100755
> --- a/tests/generic/042
> +++ b/tests/generic/042
> @@ -43,9 +43,12 @@ _crashtest()
> file=$mnt/file
> size=25M
>
> - # 25M is too small for f2fs.
> + # f2fs-utils 1.9.0 needs at least 38 MB space for f2fs image. However,
> + # f2fs-utils 1.14.0 needs at least 52 MB. Not sure if it will change
> + # again. But at least we need to configure mininum size of f2fs image
> + # to 52MB now.
It'd be better to specify a slightly bigger fs size for f2fs then. I
don't think this test depends on the fs size, just that smaller size
makes test run faster.
Maybe 64M or 128M, any suggestions from f2fs folks?
Thanks,
Eryu
> if [ $FSTYP == "f2fs" ]; then
> - size=38M
> + size=52M
> fi
>
> # Create an fs on a small, initialized image. The pattern is written to
> --
> 2.25.4
next prev parent reply other threads:[~2021-06-06 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 8:20 [PATCH] generic/042: f2fs-utils 1.14.0 needs at least 52 MB Sun Ke
2021-06-06 14:07 ` Eryu Guan [this message]
2021-06-10 12:26 ` Sun Ke
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=YLzWiH5RwHFdEWIQ@desktop \
--to=guan@eryu.me \
--cc=fstests@vger.kernel.org \
--cc=sunke32@huawei.com \
--cc=yuchao0@huawei.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