From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs-progs: handle raid56 properly
Date: Sun, 13 Nov 2022 14:32:37 +0800 [thread overview]
Message-ID: <cover.1668320935.git.wqu@suse.com> (raw)
There is a bug that "btrfs check" can fail to even open the filesystem.
The root cause is that raid56 read path doesn't even allow any missing
device, which is pretty ironic.
This patchset will fix the raid56 read path, and slightly improve the
raid56 handling (still not reaching the granularity of kernel yet).
And finally add a test case for it.
Qu Wenruo (2):
btrfs-progs: properly handle degraded raid56 reads
btrfs-progs: fsck-tests: add test case for degraded raid5
kernel-lib/bitmap.h | 45 +++++++++++++++++
kernel-shared/extent_io.c | 54 ++++++++++++---------
tests/fsck-tests/060-degraded-check/test.sh | 36 ++++++++++++++
3 files changed, 113 insertions(+), 22 deletions(-)
create mode 100644 kernel-lib/bitmap.h
create mode 100755 tests/fsck-tests/060-degraded-check/test.sh
--
2.38.1
next reply other threads:[~2022-11-13 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 6:32 Qu Wenruo [this message]
2022-11-13 6:32 ` [PATCH 1/2] btrfs-progs: properly handle degraded raid56 reads Qu Wenruo
2022-11-13 6:32 ` [PATCH 2/2] btrfs-progs: fsck-tests: add test case for degraded raid5 Qu Wenruo
2022-11-14 20:39 ` [PATCH 0/2] btrfs-progs: handle raid56 properly 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.1668320935.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