From: Scott Talbert <scott.talbert@hgst.com>
To: Filipe Manana <fdmanana@gmail.com>
Cc: Yauhen Kharuzhy <yauhen.kharuzhy@zavadatar.com>,
Scott Talbert <scott.talbert@hgst.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Device replace issues and disabling it until they are solved
Date: Thu, 2 Jun 2016 09:58:13 -0400 [thread overview]
Message-ID: <alpine.DEB.2.10.1606020955520.11959@dispatch> (raw)
In-Reply-To: <CAL3q7H7FpwMnLded9aCrt3EhFiAG5y67k2jrKjvZbn4V=rT+uQ@mail.gmail.com>
On Thu, 2 Jun 2016, Filipe Manana wrote:
> On Thu, Jun 2, 2016 at 11:03 AM, Yauhen Kharuzhy
> <yauhen.kharuzhy@zavadatar.com> wrote:
>> On Fri, May 27, 2016 at 10:43:47AM +0100, Filipe Manana wrote:
>>>> Hi Filipe,
>>>
>>> Hi Scott,
>>>
>>>>
>>>> Does your recent patch set (from May 20) address all of these issues?
>>>
>>> Yes.
>>
>> Tested, RAID5/6 still produces a plenty of 'failed to rebuild valid
>> logical NNNNNN" messages after two consecutive device replaces. So,
>> replace is still not usable for RAID5/6. And it is very slow in
>> comparison with 'device add && balance device remove missing' sequence
>> (4x slower).
>
> Right. There's missing code for raid5/6 I believe. I didn't care about
> that, nor will in the near future at least.
> The set of problems I tried to solve were generic and unrelated to any
> specific raid mode.
Back to your original question, then...should replace be disabled for
raid5/6 until it is fixed?
Scott
prev parent reply other threads:[~2016-06-02 13:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 9:09 Device replace issues and disabling it until they are solved Filipe Manana
2016-05-11 9:29 ` Qu Wenruo
2016-05-11 9:39 ` Filipe Manana
2016-05-11 15:13 ` Filipe Manana
2016-05-26 19:09 ` Scott Talbert
2016-05-27 9:43 ` Filipe Manana
2016-06-02 10:03 ` Yauhen Kharuzhy
2016-06-02 10:05 ` Filipe Manana
2016-06-02 13:58 ` Scott Talbert [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=alpine.DEB.2.10.1606020955520.11959@dispatch \
--to=scott.talbert@hgst.com \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=yauhen.kharuzhy@zavadatar.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).