From: Eric Biggers via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Eric Biggers <ebiggers@google.com>,
fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: [xfstests-bld PATCH] test-appliance: support f2fs-tools v1.9 and later
Date: Thu, 5 Apr 2018 15:21:41 -0700 [thread overview]
Message-ID: <20180405222141.42376-1-ebiggers@google.com> (raw)
Pass the -f option to mkfs.f2fs when it appears to support it. This is
required by f2fs-tools v1.9 and later in order to format the filesystem
even when an existing filesystem is detected. But earlier versions did
not accept this option.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
kvm-xfstests/test-appliance/files/root/fs/f2fs/config | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/kvm-xfstests/test-appliance/files/root/fs/f2fs/config b/kvm-xfstests/test-appliance/files/root/fs/f2fs/config
index 45fb2dd..0efcb76 100644
--- a/kvm-xfstests/test-appliance/files/root/fs/f2fs/config
+++ b/kvm-xfstests/test-appliance/files/root/fs/f2fs/config
@@ -20,6 +20,10 @@ function format_filesystem()
local dev="$1"
local opts="$2"
+ if grep -q 'force overwrite' /sbin/mkfs.f2fs; then
+ # f2fs-tools v1.9+
+ opts+=" -f"
+ fi
/sbin/mkfs.f2fs -q $opts "$dev"
return $?
}
--
2.17.0.484.g0c8726318c-goog
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next reply other threads:[~2018-04-05 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 22:21 Eric Biggers via Linux-f2fs-devel [this message]
2018-04-06 13:30 ` [xfstests-bld PATCH] test-appliance: support f2fs-tools v1.9 and later Theodore Y. Ts'o
2018-04-09 19:00 ` Eric Biggers via Linux-f2fs-devel
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=20180405222141.42376-1-ebiggers@google.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=ebiggers@google.com \
--cc=fstests@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).