From: Chao Yu <chao@kernel.org>
To: Sun Ke <sunke32@huawei.com>, fstests@vger.kernel.org, guan@eryu.me
Cc: jaegeuk@kernel.org, david@fromorbit.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] generic/066: attr1 is still there after log replay on f2fs
Date: Mon, 28 Mar 2022 11:48:38 +0800 [thread overview]
Message-ID: <16c081ae-fc87-c9d5-0bac-3482f68c58d5@kernel.org> (raw)
In-Reply-To: <20220323083724.55902-1-sunke32@huawei.com>
On 2022/3/23 16:37, Sun Ke via Linux-f2fs-devel wrote:
> The test fail on f2fs:
> xattr names and values after second fsync log replay:
> # file: SCRATCH_MNT/foobar
> +user.attr1="val1"
> user.attr3="val3"
>
> attr1 is still there after log replay. f2fs doesn't support fs-op level
> transaction functionality. so it have no way to persist all metadata
> updates in one transaction. We can use "fastboot" mountoption for this
> case, so during last fsync on qwerty, f2fs can trigger a checkpoint
> which will persist all metadata updates before fsync().
>
> Suggested-by: Chao Yu <chao@kernel.org>
> Signed-off-by: Sun Ke <sunke32@huawei.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
prev parent reply other threads:[~2022-03-28 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 8:37 [f2fs-dev] [PATCH v3] generic/066: attr1 is still there after log replay on f2fs Sun Ke via Linux-f2fs-devel
2022-03-28 3:48 ` Chao Yu [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=16c081ae-fc87-c9d5-0bac-3482f68c58d5@kernel.org \
--to=chao@kernel.org \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=sunke32@huawei.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;
as well as URLs for NNTP newsgroup(s).