From: "Dan Williams" <dan.j.williams@intel.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: Bill Davidsen <davidsen@tmr.com>,
mingo@redhat.com, neilb@suse.de, linux-raid@vger.kernel.org
Subject: Re: raid6 rebuild
Date: Thu, 5 Apr 2007 09:59:10 -0700 [thread overview]
Message-ID: <e9c3a7c20704050959t7a1866b3j8e3bcc64a893854c@mail.gmail.com> (raw)
In-Reply-To: <20070405140626.GA8726@xi.wantstofly.org>
On 4/5/07, Lennert Buytenhek <buytenh@wantstofly.org> wrote:
> On Thu, Apr 05, 2007 at 09:54:14AM -0400, Bill Davidsen wrote:
>
> > I confess, I would feel safer with my data if the rebuild started
> > over, I would like to be sure that when it (finally) finishes the
> > data are valid.
>
> With disk #3 about to die, I'd have felt safer if it first finished
> rebuilding the replacement disk for failed disk #1 (that rebuild had
> almost completed at that point), safeguarding the array against a
> third disk failure.
>
I agree, the current arrangement seems to throw away a significant
amount of work. Yes, you will need to resync when re-adding the
second disk, but in the meantime might as well try to get a redundant
mode at all costs.
> Yeah, I know, you're not supposed to lose three disks within one day.
>
>
> > If you replaced the 2nd drive, then a full rebuild would be required
> > in any case, to get ALL drives valid.
>
> You could finish the last little bit of the resync of the replacement
> for failed disk #1 (by looking at P+Q), and then re-sync the replacement
> for failed disk #2 (by looking only at P..)
> -
--
Dan
next prev parent reply other threads:[~2007-04-05 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 19:46 raid6 rebuild Lennert Buytenhek
2007-04-05 3:22 ` Dan Williams
2007-04-05 5:50 ` Lennert Buytenhek
2007-04-05 13:54 ` Bill Davidsen
2007-04-05 14:06 ` Lennert Buytenhek
2007-04-05 16:59 ` Dan Williams [this message]
2007-04-11 1:43 ` Neil Brown
2007-04-05 6:03 ` Gordon Henderson
2007-04-05 6:21 ` Lennert Buytenhek
2007-04-05 8:15 ` Gordon Henderson
2007-04-05 8:48 ` Lennert Buytenhek
2007-04-05 10:13 ` Andre Noll
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=e9c3a7c20704050959t7a1866b3j8e3bcc64a893854c@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=buytenh@wantstofly.org \
--cc=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@suse.de \
/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).