From: David Sterba <dsterba@suse.cz>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2 RESEND] Btrfs: make raid6 rebuild retry more
Date: Fri, 5 Jan 2018 13:51:15 +0100 [thread overview]
Message-ID: <20180105125115.GH3553@twin.jikos.cz> (raw)
In-Reply-To: <20180102203642.14105-1-bo.li.liu@oracle.com>
On Tue, Jan 02, 2018 at 01:36:41PM -0700, Liu Bo wrote:
> There is a scenario that can end up with rebuild process failing to
> return good content, i.e.
> suppose that all disks can be read without problems and if the content
> that was read out doesn't match its checksum, currently for raid6
> btrfs at most retries twice,
>
> - the 1st retry is to rebuild with all other stripes, it'll eventually
> be a raid5 xor rebuild,
> - if the 1st fails, the 2nd retry will deliberately fail parity p so
> that it will do raid6 style rebuild,
>
> however, the chances are that another non-parity stripe content also
> has something corrupted, so that the above retries are not able to
> return correct content, and users will think of this as data loss.
> More seriouly, if the loss happens on some important internal btree
> roots, it could refuse to mount.
>
> This extends btrfs to do more retries and each retry fails only one
> stripe. Since raid6 can tolerate 2 disk failures, if there is one
> more failure besides the failure on which we're recovering, this can
> always work.
>
> The worst case is to retry as many times as the number of raid6 disks,
> but given the fact that such a scenario is really rare in practice,
> it's still acceptable.
>
> Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
1 and added to for-next.
prev parent reply other threads:[~2018-01-05 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 20:36 [PATCH 1/2 RESEND] Btrfs: make raid6 rebuild retry more Liu Bo
2018-01-02 20:36 ` [PATCH 2/2] Btrfs: fix scrub to repair raid6 corruption Liu Bo
2018-01-05 12:51 ` David Sterba [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=20180105125115.GH3553@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=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).