From: Michael Evans <mjevans1983@gmail.com>
To: John Robinson <john.robinson@anonymous.org.uk>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: emergency call for help: raid5 fallen apart
Date: Thu, 25 Feb 2010 18:42:51 -0800 [thread overview]
Message-ID: <4877c76c1002251842g1a3b2f91ka7a825fd99a4ec18@mail.gmail.com> (raw)
In-Reply-To: <4B86C207.6030304@anonymous.org.uk>
On Thu, Feb 25, 2010 at 10:31 AM, John Robinson
<john.robinson@anonymous.org.uk> wrote:
> On 25/02/2010 17:41, Dawning Sky wrote:
>>
>> On Thu, Feb 25, 2010 at 8:45 AM, John Robinson
>> <john.robinson@anonymous.org.uk> wrote:
>>>
>>> On 25/02/2010 08:05, Giovanni Tessore wrote:
>>> [...]
>>> I do think we urgently need the hot reconstruction/recovery feature, so
>>> failing drives can be recovered to fresh drives with two sources of data,
>>> i.e. both the failing drive and the remaining drives in the array, giving
>>> us
>>> two chances of recovering every sector.
>>
>> I was one of those 4 cases in the part month. I would have certainly
>> benefited from this when I tried to replace a failing drive on my old
>> raid-5. But I think actually the redundancy you desired can be
>> achieved by running a raid-6 at the degraded mode (with 1 missing
>> drive).
>>
>> Do I miss something? If this is the case, shouldn't we all
>> be doing this instead of using the raid-5?
>
> I think you must be missing something, yes. RAID-6 with one drive missing
> would have 2 chances of recovering each sector, but then so does RAID-5 with
> no drives missing. In either case, lose a drive and you need every sector on
> the remaining drives to be good to complete the reconstruction and keep the
> array up.
>
> Cheers,
>
> John.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
No, what they're saying is that often drives don't /totally/ fail.
They have segments that go bad first, and we are often catching them
in that state. To use the segments that /are/ successfully returned
there is a good chance that multiple 'not full member' drive could
provide a complete, or usefully very near complete with known 'dead'
areas set to store on fresh devices.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-02-26 2:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 14:54 emergency call for help: raid5 fallen apart Stefan G. Weichinger
2010-02-24 15:05 ` Stefan G. Weichinger
2010-02-24 15:22 ` Robin Hill
2010-02-24 15:32 ` Stefan G. Weichinger
2010-02-24 16:38 ` Stefan G. Weichinger
2010-02-24 16:53 ` Stefan G. Weichinger
2010-02-24 17:02 ` Stefan G. Weichinger
2010-02-25 8:05 ` Giovanni Tessore
2010-02-25 16:27 ` Stefan /*St0fF*/ Hübner
2010-02-25 16:45 ` John Robinson
2010-02-25 17:41 ` Dawning Sky
2010-02-25 18:31 ` John Robinson
2010-02-26 2:42 ` Michael Evans [this message]
2010-02-26 20:15 ` Bill Davidsen
2010-02-28 11:50 ` Stefan /*St0fF*/ Hübner
2010-02-28 12:52 ` Stefan /*St0fF*/ Hübner
2010-02-24 17:09 ` Robin Hill
2010-02-24 17:28 ` Stefan G. Weichinger
2010-02-24 17:35 ` Stefan G. Weichinger
2010-02-24 18:12 ` Robin Hill
2010-02-24 19:54 ` Stefan G. Weichinger
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=4877c76c1002251842g1a3b2f91ka7a825fd99a4ec18@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=john.robinson@anonymous.org.uk \
--cc=linux-raid@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).