linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: Shai <shaibn@gmail.com>
Cc: Dexter Filmore <Dexter.Filmore@gmx.de>, linux-raid@vger.kernel.org
Subject: Re: replace disk in raid5 without linux noticing?
Date: Wed, 19 Apr 2006 13:03:42 -0400	[thread overview]
Message-ID: <1145466223.8608.84.camel@localhost.localdomain> (raw)
In-Reply-To: <e3edb0fa0604190931i1160d94eo829ba17943b0c5eb@mail.gmail.com>

On Wed, 2006-04-19 at 18:31 +0200, Shai wrote:
> On 4/19/06, Dexter Filmore <Dexter.Filmore@gmx.de> wrote:
> > Let's say a disk in an array starts yielding smart errors but is still
> > functional.
> > So instead of waiting for it to fail completely and start a sync and stress
> > the other disks, could I clone that disk to a fresh one, put the array
> > offline and replace the disk?
> 
> Hi,
> 
> Why can't you just mark that drive as failed, remove it and hotadd a
> new drive to replace the failed drive?

because background rebuild is slower than disk to disk copy, since his
disk is still fully functional.


> 
> Shai
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2006-04-19 17:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19 14:31 replace disk in raid5 without linux noticing? Dexter Filmore
2006-04-19 16:31 ` Shai
2006-04-19 17:03   ` Ming Zhang [this message]
2006-04-19 17:41     ` Brendan Conoboy
2006-04-19 18:16       ` Ming Zhang
2006-04-20 15:22         ` Gabor Gombas
2006-04-20 15:24           ` Ming Zhang
2006-04-21 18:23   ` Dexter Filmore
2006-04-21 22:25     ` Carlos Carvalho
2006-04-22 15:08       ` Martin Cracauer
2006-04-22 17:48         ` Carlos Carvalho
2006-04-23 16:43           ` Martin Cracauer

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=1145466223.8608.84.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --cc=Dexter.Filmore@gmx.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=shaibn@gmail.com \
    /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).