From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Christoph Hellwig <hch@infradead.org>, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
Askar Safin <safinaskar@gmail.com>
Subject: Re: [PATCH RFC 2/2] fs: fully sync all fses even for an emergency sync
Date: Tue, 4 Nov 2025 07:16:53 +1030 [thread overview]
Message-ID: <5f7590e5-1c18-4e48-a643-c0ab1350c6a7@gmx.com> (raw)
In-Reply-To: <aQiaXVkz1QYkMsWA@infradead.org>
在 2025/11/3 22:34, Christoph Hellwig 写道:
> Forgot to add, but I think the main issue here is that btrfs clears the
> writeback flag on the folio before commiting the metadata for the
> writeback.
During my debug runs, the metadata are properly written back to storage,
during the sync_inodes_one_sb() calls.
So that doesn't seem to be the problem.
> I tried to fix this a few years ago, and IIRC Josef tried
> again a few month ago. If that is fixed, even a non-blocking writeback
> will commit all the updates it actually kicked off, just like for other
> file systems. (It will also sort out all kinds of annoying locking
> issues)
The problem is still there, even if all new metadata are committed, the
super block is still not, thus after a power loss we are still seeing
the old metadata, not the newer ones.
Thanks,
Qu
next prev parent reply other threads:[~2025-11-03 20:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 4:07 [PATCH RFC 0/2] fs: fully sync all fsese even for an emergency sync Qu Wenruo
2025-11-03 4:07 ` [PATCH RFC 1/2] fs: do not pass a parameter for sync_inodes_one_sb() Qu Wenruo
2025-11-03 11:51 ` Christoph Hellwig
2025-11-04 8:42 ` Jan Kara
2025-11-05 18:50 ` Daniel Vacek
2025-11-03 4:07 ` [PATCH RFC 2/2] fs: fully sync all fses even for an emergency sync Qu Wenruo
2025-11-03 11:56 ` Christoph Hellwig
2025-11-03 12:04 ` Christoph Hellwig
2025-11-03 20:46 ` Qu Wenruo [this message]
2025-11-03 20:55 ` Qu Wenruo
2025-11-04 8:28 ` Jan Kara
2025-11-04 8:39 ` Jan Kara
2025-11-05 11:32 ` Christian Brauner
2025-11-04 8:43 ` Qu Wenruo
2025-11-04 12:42 ` Jan Kara
2025-11-04 15:48 ` Christoph Hellwig
2025-11-03 16:00 ` [PATCH RFC 0/2] fs: fully sync all fsese " Askar Safin
2025-11-05 11:31 ` Christian Brauner
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=5f7590e5-1c18-4e48-a643-c0ab1350c6a7@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=brauner@kernel.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=safinaskar@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wqu@suse.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