From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: David Greaves <david@dgreaves.com>, linux-raid@vger.kernel.org
Subject: Re: How to avoid complete rebuild of RAID 6 array (6/8 active devices)
Date: Tue, 15 Jul 2008 16:24:50 +0200 [thread overview]
Message-ID: <20080715142450.GA21485@rap.rap.dk> (raw)
In-Reply-To: <20080714225816.GS4314@kiste.smurf.noris.de>
On Tue, Jul 15, 2008 at 12:58:16AM +0200, Matthias Urlichs wrote:
> Hi,
>
> However, even if they do in fact continue to deteriorate, the ability to
> re-map the offending areas and continue gives me an order of magnitude
> more time to deal with the problem.
>
> In fact, as I said, there may be problems lurking on other disks which I
> just haven't found yet (how often do you read all 5TB of your data?),
> which means that a feature like this is the difference between being
> able to recover and certain data loss, RAID-6 nonwithstanding.
One idea about this - One could read and write the disks perodically,
say once a month. In this way single bit errors that could have evolved
on the disks coule be repaired, as the CRC saves the one bit error, and
gets it corrected when writing. For a raid - if an error occurs, then
the sound data could be used, and if the error persists after a rewrite
on the bad disk, that data should then be remapped to a sound area on
the drive. Maybe people already have implemented this. SMART data could
also be consulted.
I thought of badblocks -n to do this, but also raid check could be a
place to do it. When writing ons should of cause take care that nobody
else is writing the same data.
best regards
keld
prev parent reply other threads:[~2008-07-15 14:24 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
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 [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=20080715142450.GA21485@rap.rap.dk \
--to=keld@dkuug.dk \
--cc=david@dgreaves.com \
--cc=linux-raid@vger.kernel.org \
--cc=smurf@smurf.noris.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 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.