From: Richard Palethorpe <rpalethorpe@suse.de>
To: Jie2x Zhou <jie2x.zhou@intel.com>
Cc: Philip Li <philip.li@intel.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] test_robind.sh: fix BROK: mkfs.f2fs /dev/sdb1 failed
Date: Tue, 15 Nov 2022 10:15:17 +0000 [thread overview]
Message-ID: <87cz9osens.fsf@suse.de> (raw)
In-Reply-To: <20221114062008.999566-1-jie2x.zhou@intel.com>
Hello,
Merged, thanks!
Jie2x Zhou <jie2x.zhou@intel.com> writes:
> Error output:
> test_robind 1 TINFO: Formatting /dev/sda1 with f2fs extra opts=''
>
> F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
>
> Info: Disable heap-based policy
> Info: Debug level = 0
> Info: Trim is enabled
> /dev/sda1 appears to contain an existing filesystem (f2fs).
> Use the -f option to force overwrite.
> test_robind 1 TBROK: mkfs.f2fs /dev/sda1 failed
>
> Reason:
> Test error is caused by miss "-f" option when do mkfs.f2fs.
>
> Signed-off-by: Jie2x Zhou <jie2x.zhou@intel.com>
> ---
> testcases/kernel/fs/fs_readonly/test_robind.sh | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/testcases/kernel/fs/fs_readonly/test_robind.sh b/testcases/kernel/fs/fs_readonly/test_robind.sh
> index bab2648f4..2d9a87b7e 100755
> --- a/testcases/kernel/fs/fs_readonly/test_robind.sh
> +++ b/testcases/kernel/fs/fs_readonly/test_robind.sh
> @@ -200,6 +200,8 @@ for fstype in $FSTYPES; do
> opts="-F"
> elif [ "$fstype" = "xfs" ]; then
> opts="-f"
> + elif [ "$fstype" = "f2fs" ]; then
> + opts="-f"
> elif [ "$fstype" = "btrfs" ]; then
> opts="-f"
> fi
> --
> 2.38.1
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-11-15 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 6:20 [LTP] [PATCH] test_robind.sh: fix BROK: mkfs.f2fs /dev/sdb1 failed Jie2x Zhou
2022-11-15 10:15 ` Richard Palethorpe [this message]
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=87cz9osens.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=jie2x.zhou@intel.com \
--cc=ltp@lists.linux.it \
--cc=philip.li@intel.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