From: Chao Yu <chao@kernel.org>
To: Jan Prusakowski <jprusakowski@google.com>,
zlang@kernel.org, fstests@vger.kernel.org
Cc: wqu@suse.com, anand.jain@oracle.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] generic/050: handle f2fs as nojournal filesystem
Date: Fri, 17 Apr 2026 02:59:02 +0000 [thread overview]
Message-ID: <0c24f215-54d4-457c-adbe-e03c815382c2@kernel.org> (raw)
In-Reply-To: <20260410131821.991005-1-jprusakowski@google.com>
On 4/10/26 13:18, Jan Prusakowski via Linux-f2fs-devel wrote:
> F2FS uses a checkpoint mechanism for metadata consistency rather than a
> traditional journal. Roll-forward recovery is only needed if there are
> fsync'd files since the last checkpoint.
>
> In this test case, files are created without fsync, so there is no
> roll-forward data to replay during mount.
>
> Therefore, F2FS does not need to write to the device to recover, and
> successfully mounts on the read-only block device. Thus, it should be
> treated as nojournal in this case.
>
> Signed-off-by: Jan Prusakowski <jprusakowski@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jan Prusakowski <jprusakowski@google.com>,
zlang@kernel.org, fstests@vger.kernel.org
Cc: anand.jain@oracle.com, wqu@suse.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] generic/050: handle f2fs as nojournal filesystem
Date: Fri, 17 Apr 2026 02:59:02 +0000 [thread overview]
Message-ID: <0c24f215-54d4-457c-adbe-e03c815382c2@kernel.org> (raw)
In-Reply-To: <20260410131821.991005-1-jprusakowski@google.com>
On 4/10/26 13:18, Jan Prusakowski via Linux-f2fs-devel wrote:
> F2FS uses a checkpoint mechanism for metadata consistency rather than a
> traditional journal. Roll-forward recovery is only needed if there are
> fsync'd files since the last checkpoint.
>
> In this test case, files are created without fsync, so there is no
> roll-forward data to replay during mount.
>
> Therefore, F2FS does not need to write to the device to recover, and
> successfully mounts on the read-only block device. Thus, it should be
> treated as nojournal in this case.
>
> Signed-off-by: Jan Prusakowski <jprusakowski@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-04-17 2:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 13:18 [PATCH] generic/050: handle f2fs as nojournal filesystem Jan Prusakowski
2026-04-10 13:18 ` [f2fs-dev] " Jan Prusakowski via Linux-f2fs-devel
2026-04-14 7:57 ` Christoph Hellwig
2026-04-14 7:57 ` [f2fs-dev] " Christoph Hellwig
2026-04-16 16:47 ` Zorro Lang
2026-04-16 16:47 ` [f2fs-dev] " Zorro Lang
2026-04-17 7:42 ` Christoph Hellwig
2026-04-17 7:42 ` [f2fs-dev] " Christoph Hellwig
2026-04-16 16:44 ` Zorro Lang
2026-04-16 16:44 ` [f2fs-dev] " Zorro Lang
2026-04-17 2:59 ` Chao Yu [this message]
2026-04-17 2:59 ` Chao Yu 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=0c24f215-54d4-457c-adbe-e03c815382c2@kernel.org \
--to=chao@kernel.org \
--cc=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=jprusakowski@google.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=wqu@suse.com \
--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 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.