All of lore.kernel.org
 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: Wed, 30 Jun 2004 10:44:44 +0200	[thread overview]
Message-ID: <40E27D7C.2040101@conterra.de> (raw)
In-Reply-To: <200406300219.i5U2JW327038@watkins-home.com>

Guy wrote:
> I don't think plan b needs to be handled as stated.  If a cable is loose,
> the amount of data that needs to be written somewhere else could be vast.
> At least as big as 1 disk! 

agreed; any such "active" bad block replacement will only postpone the
problem. It will never be able to solve the problem absolutely reliable.
I also agree, that it makes the system more complex and may need some
manual intervention, too.

> That brings me back to:
> If the hard drive can't re-locate the bad block, then, accept that you have
> had a failure.

completely true. Kick off the bad disk and rebuild a new one sound
easy and save. But it is not! Before/during rebuild, your raid system runs
unprotected in a very fragile state, even more fragile than a single
disk system without raid! Thus the additional spare blocks may help
to bridge over this phase more safely. Thus this is not an alternative
of replacing the bad disk; you will do that, definitely!
Instead it is just an addition.

If you are hanging on a rope on a cliff, and notice, that the rope
shows a defect, what will you do? Cut it off, before it breaks
completely! and while falling, you may inspect your backpack to
find a spare rope to use.....

Dieter.

  reply	other threads:[~2004-06-30  8:44 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
2004-06-29 23:45         ` Mike Tran
2004-06-30  2:19           ` Guy
2004-06-30  8:44             ` Dieter Stueken [this message]
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=40E27D7C.2040101@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 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.