linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: linux-raid@vger.kernel.org
Subject: bad block checking and repair
Date: Thu, 23 Oct 2008 14:31:17 +0200	[thread overview]
Message-ID: <20081023123117.GA24775@rap.rap.dk> (raw)

Is there a case for better bad block handling in linux raid?

Disk errors are reported to be more and more frequent in today's
systems. Storage capacity grows and with that the likelihood of disk
errors.

I am not sure of the ststus of bad block handling in linux raid.
Can somebody enlighten me?

I think there are a number of techniques that could be employed.

1. checking an array - full scan, and occasionally examining the SMART
error log, eg. every gigabyte, then rewrite the data with reported
errors. Then check the SMART error log again and for the errors still
reported move it to a bad block area and remap the affected data.

2. When irrecoverable errors have occurred, then check which drive was
affected, and remap the bad data on the bad disk, using the data of the
sound drive (for raids with redundant data). 

Is this viable techniques? I think something like this could be built
into the raid check functionality.

best regards
keld

                 reply	other threads:[~2008-10-23 12:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20081023123117.GA24775@rap.rap.dk \
    --to=keld@dkuug.dk \
    --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).