All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sun Ke <sunke32@huawei.com>
To: <fstests@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>, <guan@eryu.me>,
	<yuchao0@huawei.com>
Cc: <sunke32@huawei.com>
Subject: [PATCH v3] generic/042: make a bigger img for f2fs
Date: Tue, 15 Jun 2021 11:16:15 +0800	[thread overview]
Message-ID: <20210615031615.4173039-1-sunke32@huawei.com> (raw)

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.
So, just set it to 128M.

Signed-off-by: Sun Ke <sunke32@huawei.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
---
 tests/generic/042 | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/tests/generic/042 b/tests/generic/042
index ee0e4b400c71..6437ef0724b7 100755
--- a/tests/generic/042
+++ b/tests/generic/042
@@ -43,9 +43,11 @@ _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. So just set it 128M.
 	if [ $FSTYP == "f2fs" ]; then
-		size=38M
+		size=128M
 	fi
 
 	# Create an fs on a small, initialized image. The pattern is written to
-- 
2.25.4


WARNING: multiple messages have this Message-ID (diff)
From: Sun Ke <sunke32@huawei.com>
To: <fstests@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>, <guan@eryu.me>,
	<yuchao0@huawei.com>
Cc: sunke32@huawei.com
Subject: [f2fs-dev] [PATCH v3] generic/042: make a bigger img for f2fs
Date: Tue, 15 Jun 2021 11:16:15 +0800	[thread overview]
Message-ID: <20210615031615.4173039-1-sunke32@huawei.com> (raw)

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.
So, just set it to 128M.

Signed-off-by: Sun Ke <sunke32@huawei.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
---
 tests/generic/042 | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/tests/generic/042 b/tests/generic/042
index ee0e4b400c71..6437ef0724b7 100755
--- a/tests/generic/042
+++ b/tests/generic/042
@@ -43,9 +43,11 @@ _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. So just set it 128M.
 	if [ $FSTYP == "f2fs" ]; then
-		size=38M
+		size=128M
 	fi
 
 	# Create an fs on a small, initialized image. The pattern is written to
-- 
2.25.4



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

             reply	other threads:[~2021-06-15  3:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15  3:16 Sun Ke [this message]
2021-06-15  3:16 ` [f2fs-dev] [PATCH v3] generic/042: make a bigger img for f2fs 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=20210615031615.4173039-1-sunke32@huawei.com \
    --to=sunke32@huawei.com \
    --cc=fstests@vger.kernel.org \
    --cc=guan@eryu.me \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.