From: Liu Bo <bo.li.liu@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] Fix raid6 reconstruction bug
Date: Wed, 1 Nov 2017 18:54:01 -0600 [thread overview]
Message-ID: <20171102005405.20420-1-bo.li.liu@oracle.com> (raw)
This is an attempt to fix a raid6 bug, that is, if two disks got
hotplugged at run time, reconstruction process is not able to rebuild
correct data to use even if raid6 can theoretically tolerate two disk
failure.
Patch 1 is a preparation patch, which introduces the necessary flags
and flag handling.
More details about the above bug can be found in Patch 2.
Patch 3 applies flags to raid1/10 profile.
Patch 4 fixes btrfs to show flags for each device correctly.
A test case[1] for fstests has been sent out.
[1]: fstests: btrfs: add test case for raid6 reconstruction bug
https://patchwork.kernel.org/patch/10037769/
Liu Bo (4):
Btrfs: introduce device flags
Btrfs: fix data corruption in raid6
Btrfs: make raid1 and raid10 be aware of device flag In_sync
Btrfs: change how we set In_sync
fs/btrfs/disk-io.c | 21 ++++++++++++++++-
fs/btrfs/raid56.c | 3 ++-
fs/btrfs/volumes.c | 68 ++++++++++++++++++++++++++++++++++++++++++++++--------
fs/btrfs/volumes.h | 8 +++++++
4 files changed, 88 insertions(+), 12 deletions(-)
--
2.9.4
next reply other threads:[~2017-11-02 1:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 0:54 Liu Bo [this message]
2017-11-02 0:54 ` [PATCH 1/4] Btrfs: introduce device flags Liu Bo
2017-11-06 16:40 ` David Sterba
2017-11-08 19:46 ` Liu Bo
2017-11-13 17:13 ` David Sterba
2017-11-07 9:30 ` Anand Jain
2017-11-02 0:54 ` [PATCH 2/4] Btrfs: fix data corruption in raid6 Liu Bo
2017-11-07 8:32 ` Anand Jain
2017-11-08 19:53 ` Liu Bo
2017-11-09 9:29 ` Anand Jain
2017-11-09 9:59 ` Qu Wenruo
2017-11-10 0:12 ` Liu Bo
2017-11-10 0:54 ` Qu Wenruo
2017-11-10 10:15 ` Qu Wenruo
2017-11-02 0:54 ` [PATCH 3/4] Btrfs: make raid1 and raid10 be aware of device flag In_sync Liu Bo
2017-11-02 0:54 ` [PATCH 4/4] Btrfs: change how we set In_sync Liu Bo
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=20171102005405.20420-1-bo.li.liu@oracle.com \
--to=bo.li.liu@oracle.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;
as well as URLs for NNTP newsgroup(s).