From: Jaegeuk Kim <jaegeuk@kernel.org>
To: "S." <sb56637@gmail.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] mkfs.f2fs -f to reformat Btrfs partition doesn't change FS type
Date: Fri, 10 Sep 2021 15:58:50 -0700 [thread overview]
Message-ID: <YTvjKmf/dxzuDemP@google.com> (raw)
In-Reply-To: <75f47f9c-4587-9105-81bd-38708df8fab9@gmail.com>
On 09/07, S. wrote:
> Hi there, I develop Linux spins based on openSUSE Tumbleweed. Currently the base system has Linux 5.14.0 and f2fs-tools 1.14.0. There is a bug that I can consistently reproduce with:
> # mkfs.f2fs -f /dev/sda1
> When the prior filesystem of /dev/sda1 is Btrfs, the `mkfs.f2fs` command is successful, but the filesystem type remains "Btrfs". Then the filesystem can be manually mounted with `mount -t f2fs ####` but only manually, the wrong FS type confuses the Linux boot process and won't allow it to mount in the case of a root partition. This appears to only happen when the previous filesystem is Btrfs. I have tested this bug to *not* occur when the previous filesystem is EXT4 and XFS.
It seems mkfs.f2fs didn't wipe the BTRFS magic since that is unused critical
space in f2fs. Anyway, I think it's worth to fix it.
https://lore.kernel.org/linux-f2fs-devel/20210910225618.501839-1-jaegeuk@kernel.org/T/#u
> Thanks a lot!
>
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2021-09-10 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 13:18 [f2fs-dev] mkfs.f2fs -f to reformat Btrfs partition doesn't change FS type S.
2021-09-10 22:58 ` Jaegeuk Kim [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=YTvjKmf/dxzuDemP@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=sb56637@gmail.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.