Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Tommy Apel Hansen <tommyapeldk@gmail.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: Suggestion for hot-replace
Date: Sun, 25 Nov 2012 16:36:34 +0100	[thread overview]
Message-ID: <4164037.TSORKSTxib@workstation-home> (raw)
In-Reply-To: <10107277.2.1353857505404.JavaMail.root@zimbra>

On Sunday 25 November 2012 16:31:45 Roy Sigurd Karlsbakk wrote:
> > Hello, personally I would vote for an option to rotate spares into and
> > array
> > like Peter suggests, keeping a drive idle doesn't guarrantee that it's
> > actually operational.
> 
> Only problem with this, is if you do it frequently, it'll degrade
> performance.
> 
> Btw, is there a way to replace a drive without failing one? In RAID-5, a
> common issue is to have a failed drive and then find bad sectors on
> another. In this setting (and possibly others), it'd be good to have md
> replace the drive while still active (like what can be done in ZFS).

Well both options serve a purpose, but say you rotate a spare into the array 
that then fails on spinup, then you would have a faulted array as your 
implementation plan states that a drive cannot be "older" than x hours, then 
you would have and endless loop where as the other option would suggest to 
zero the former drive and reinstate it.

/Tommy

  reply	other threads:[~2012-11-25 15:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-25  6:37 Suggestion for hot-replace H. Peter Anvin
2012-11-25 10:13 ` Piergiorgio Sartor
2012-11-25 12:31   ` Tommy Apel Hansen
2012-11-25 14:51     ` Piergiorgio Sartor
2012-11-25 15:31     ` Roy Sigurd Karlsbakk
2012-11-25 15:36       ` Tommy Apel Hansen [this message]
2012-11-25 15:42         ` Piergiorgio Sartor
2012-11-25 18:01       ` Mikael Abrahamsson
2012-11-25 17:59 ` joystick
2012-11-25 21:49   ` NeilBrown
2012-11-25 23:43     ` H. Peter Anvin
2012-11-26  1:46       ` 王金浦

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=4164037.TSORKSTxib@workstation-home \
    --to=tommyapeldk@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=roy@karlsbakk.net \
    /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