From: Chao Yu <chao@kernel.org>
To: Zorro Lang <zlang@kernel.org>, fstests@vger.kernel.org
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
Chao Yu <chao@kernel.org>
Subject: [PATCH 3/4] common/rc: support f2fs in _repair_scratch_fs
Date: Thu, 6 Mar 2025 16:18:08 +0800 [thread overview]
Message-ID: <20250306081809.2397527-3-chao@kernel.org> (raw)
In-Reply-To: <20250306081809.2397527-1-chao@kernel.org>
Support f2fs in _repair_scratch_fs(), and use -f to repair the image
forcely.
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Signed-off-by: Chao Yu <chao@kernel.org>
---
common/rc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/common/rc b/common/rc
index ca755055..bf24da4e 100644
--- a/common/rc
+++ b/common/rc
@@ -1500,6 +1500,9 @@ _repair_scratch_fs()
# want the test to fail:
_check_scratch_fs
;;
+ f2fs)
+ fsck -t $FSTYP -f $SCRATCH_DEV
+ ;;
*)
local dev=$SCRATCH_DEV
local fstyp=$FSTYP
--
2.48.1
next prev parent reply other threads:[~2025-03-06 8:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 8:18 [PATCH 1/4] common/config: remove redundant export of F2FS_IO_PROG Chao Yu
2025-03-06 8:18 ` [PATCH 2/4] common/config: export F2FS_INJECT_PROG Chao Yu
2025-03-07 3:57 ` David Disseldorp
2025-03-06 8:18 ` Chao Yu [this message]
2025-03-07 3:57 ` [PATCH 3/4] common/rc: support f2fs in _repair_scratch_fs David Disseldorp
2025-03-06 8:18 ` [PATCH 4/4] f2fs/009: detect and repair nlink corruption Chao Yu
2025-03-07 4:02 ` David Disseldorp
2025-03-10 9:46 ` Chao Yu
2025-03-10 8:00 ` Zorro Lang
2025-03-10 9:59 ` Chao Yu
2025-03-10 19:48 ` Zorro Lang
2025-03-11 2:24 ` Chao Yu
2025-03-07 3:56 ` [PATCH 1/4] common/config: remove redundant export of F2FS_IO_PROG David Disseldorp
2025-03-10 7:16 ` Zorro Lang
2025-03-10 8:02 ` Zorro Lang
2025-03-10 10:01 ` Chao Yu
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=20250306081809.2397527-3-chao@kernel.org \
--to=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=zlang@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