All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Urlichs <matthias@urlichs.de>
To: linux-raid@vger.kernel.org
Subject: Re: How to avoid complete rebuild of RAID 6 array (6/8 active devices)
Date: Mon, 14 Jul 2008 10:44:16 +0000 (UTC)	[thread overview]
Message-ID: <g5fam0$8oe$1@ger.gmane.org> (raw)
In-Reply-To: 48680586.609@tmr.com

On Sun, 29 Jun 2008 17:58:30 -0400, Bill Davidsen wrote:

> Of course build an array out of drives so unstable that you can't safelt
> *run* a check is another topic.

It's a topic that needs to be addressed sooner or later, however.

Let's face it, drives do develop bad spots.

Tossing a perfectly good drive because 0.0000064% of the data cannot be
read is wasteful (assuming a 64-kByte area of an 1-terabyte disk).

My basic approach would be, whenever a read error is encountered, to tell
the disk drive to fix the bad area (either by rewriting the problem area
or by hardware reallocation or by using devmapper), fix the data (either
tell the RAID driver that this particular area needs to be recovered or
do it in userspace), and re-add the drive.

So ... is there some userspace code which, given a bunch of RAID disks,
can rebuild the array? Limiting said rebuild to one particular area on
one particular disk should then be reasonably easy.

-- 
Matthias Urlichs


  reply	other threads:[~2008-07-14 10:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25  6:37 How to avoid complete rebuild of RAID 6 array (6/8 active devices) Dave Moon
2008-06-25 16:13 ` Andre Noll
2008-06-27 10:40   ` Neil Brown
2008-06-29 21:58     ` Bill Davidsen
2008-07-14 10:44       ` Matthias Urlichs [this message]
2008-07-14 16:14         ` David Greaves
2008-07-14 16:54           ` David Lethe
2008-07-14 22:58           ` Matthias Urlichs
2008-07-14 23:54             ` Richard Scobie
2008-07-15  0:05               ` Matthias Urlichs
2008-07-15 14:24             ` Keld Jørn Simonsen

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='g5fam0$8oe$1@ger.gmane.org' \
    --to=matthias@urlichs.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.