From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: fixes for commit 947a629988f1 ("btrfs: move tree block parentness check into validate_extent_buffer()")
Date: Thu, 29 Dec 2022 07:32:22 +0800 [thread overview]
Message-ID: <cover.1672190127.git.wqu@suse.com> (raw)
There is a regression report from Mikhail that his btrfs RAID0 fs
randomly flips to RO after commit 947a629988f1.
It turns out that, the offending commit can not handle tree blocks
crossing stripe boundary.
Although tree blocks crossing stripe boundary is not an ideal situation,
we should still be able to correctly handle it.
This patchset firstly adds the missing level mismatch error message,
then fix the offending commit.
Qu Wenruo (2):
btrfs: add error message for metadata level mismatch
btrfs: fix the false alert on bad tree level
fs/btrfs/disk-io.c | 4 ++++
fs/btrfs/extent_io.c | 31 ++++++++++++++++++++++++++-----
2 files changed, 30 insertions(+), 5 deletions(-)
--
2.39.0
next reply other threads:[~2022-12-28 23:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 23:32 Qu Wenruo [this message]
2022-12-28 23:32 ` [PATCH 1/2] btrfs: add error message for metadata level mismatch Qu Wenruo
2022-12-28 23:32 ` [PATCH 2/2] btrfs: fix the false alert on bad tree level Qu Wenruo
2023-01-02 15:14 ` David Sterba
2023-01-02 15:13 ` [PATCH 0/2] btrfs: fixes for commit 947a629988f1 ("btrfs: move tree block parentness check into validate_extent_buffer()") David Sterba
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=cover.1672190127.git.wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox