linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: linux-btrfs@vger.kernel.org
Cc: Miao Xie <miaoxie@huawei.com>, Philip <bugzilla@philip-seeger.de>
Subject: Re: [PATCH 0/4] Btrfs: RAID 5/6 missing device replace
Date: Tue, 26 May 2015 10:05:47 -0700	[thread overview]
Message-ID: <20150526170547.GA21342@mew.lv.cox.net> (raw)
In-Reply-To: <cover.1431330020.git.osandov@osandov.com>

On Mon, May 11, 2015 at 12:58:11AM -0700, Omar Sandoval wrote:
> A user reported on Bugzilla that they were seeing kernel BUGs when
> attempting to replace a missing device on a RAID 6 array. After
> identifying the apparent cause of the BUG, I reached the conclusion that
> there wasn't a quick fix. Maybe Miao Xie can point something out that I
> missed, as he originally implemented device replace on RAID 5/6 :)
> 
> Patch 4 has the details, but the main problem is that we can't create
> bios for a missing device, so the main scrub code path isn't very
> useful. On RAID 5/6, since we only have one mirror for any piece of
> data, the missing device is the only mirror we can use. Clearly, (unless
> I missed something), this case needs to be handled differently.
> 
> These patches are on top of v4.1-rc2. I ran the scrub and replace
> xfstests and the script below, which also reproduces the original BUG.
> 
> Thanks!
> 
> Omar Sandoval (4):
>   Btrfs: remove misleading handling of missing device scrub
>   Btrfs: count devices correctly in readahead during RAID 5/6 replace
>   Btrfs: add RAID 5/6 BTRFS_RBIO_REBUILD_MISSING operation
>   Btrfs: fix device replace of a missing RAID 5/6 device
> 
>  fs/btrfs/raid56.c |  87 +++++++++++++++++++++++++----
>  fs/btrfs/raid56.h |  10 +++-
>  fs/btrfs/reada.c  |   4 +-
>  fs/btrfs/scrub.c  | 164 +++++++++++++++++++++++++++++++++++++++++++++---------
>  4 files changed, 225 insertions(+), 40 deletions(-)
> 

Ping for review.

-- 
Omar

  parent reply	other threads:[~2015-05-26 17:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11  7:58 [PATCH 0/4] Btrfs: RAID 5/6 missing device replace Omar Sandoval
2015-05-11  7:58 ` [PATCH 1/4] Btrfs: remove misleading handling of missing device scrub Omar Sandoval
2015-05-11  7:58 ` [PATCH 2/4] Btrfs: count devices correctly in readahead during RAID 5/6 replace Omar Sandoval
2015-05-11  7:58 ` [PATCH 3/4] Btrfs: add RAID 5/6 BTRFS_RBIO_REBUILD_MISSING operation Omar Sandoval
2015-05-11  7:58 ` [PATCH 4/4] Btrfs: fix device replace of a missing RAID 5/6 device Omar Sandoval
2015-06-11 10:29   ` Zhao Lei
2015-06-12  8:12     ` Omar Sandoval
2015-06-12  8:26       ` Zhao Lei
2015-05-26 17:05 ` Omar Sandoval [this message]
2015-06-11  3:52   ` [PATCH 0/4] Btrfs: RAID 5/6 missing device replace Zhao Lei
2015-06-11  6:08     ` Omar Sandoval
2015-06-12  9:42       ` wangyf

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=20150526170547.GA21342@mew.lv.cox.net \
    --to=osandov@osandov.com \
    --cc=bugzilla@philip-seeger.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=miaoxie@huawei.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;
as well as URLs for NNTP newsgroup(s).