linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dieter Stueken <stueken@conterra.de>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: raid and sleeping bad sectors
Date: Tue, 29 Jun 2004 22:56:58 +0200	[thread overview]
Message-ID: <40E1D79A.5030405@conterra.de> (raw)
In-Reply-To: <1088534585.5376.118.camel@star2.austin.ibm.com>

Mike Tran wrote:
> (Please note that I don't mean to advertise EVMS here :) just want to
> mention that the functionality is available)
> 
> EVMS, (http://evms.sourceforge.net) provides a solution to this "bad
> sectors" issue by having Bad Block Relocation (BBR) layer on the I/O
> stack.

Before proposing any solutions, i think it is very important to
distinguish carefully between different kinds of errors:

a) read errors: some alert bell should ring (syslog/mail..)
    but the system should not careless disable any disk to avoid
    making the problem even worse.

b) write errors: if some blocks are written partly, but can not
    be written to all disks, it may help, to write the data
    (may be temporary) somewhere else.

when we got a read error, due to an unreadable sector, we may
first try to rewrite it. In most cases, bad sector replacement
of the HD-firmware takes action and the problem is solved so far.

Only after this failed, we should turn over to plan b)

case b) may also help, if some disk gets temporary unavailable
(i.E. cabling problem). After manual intervention, that brings
the disk back on line again, the redirected data may even be
copied back.

Dieter

  reply	other threads:[~2004-06-29 20:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 10:48 raid and sleeping bad sectors Dieter Stueken
2004-06-29 15:59 ` Guy
2004-06-29 16:30   ` John Lange
2004-06-29 18:43     ` Mike Tran
2004-06-29 20:56       ` Dieter Stueken [this message]
2004-06-29 23:45         ` Mike Tran
2004-06-30  2:19           ` Guy
2004-06-30  8:44             ` Dieter Stueken
2004-06-30 21:40             ` Mike Tran
2004-06-30 22:44               ` Guy
2004-06-30 23:27                 ` Jure Peèar
2004-07-01  1:52                   ` Guy
2004-07-01  2:42                     ` Michael Hardy
2004-06-29 21:51       ` Guy
2004-06-29 22:20         ` Mike Tran
2004-06-29 18:03   ` Guy
2004-06-29 17:37 ` dean gaudet
2004-06-30  6:12 ` Holger Kiehl

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=40E1D79A.5030405@conterra.de \
    --to=stueken@conterra.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 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).