linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: joystick <joystick@shiftmail.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Suggestion for hot-replace
Date: Sun, 25 Nov 2012 18:59:19 +0100	[thread overview]
Message-ID: <50B25C77.4000502@shiftmail.org> (raw)
In-Reply-To: <50B1BCBD.70306@zytor.com>

On 11/25/12 07:37, H. Peter Anvin wrote:
> I was looking at the hot-replace (want_replacement) feature, and I had 
> a thought: it would be nice to have this in a form which *didn't* fail 
> the incumbent drive after the operation is over, and instead turned it 
> into a spare.  This would make it much easier and safer to 
> periodically rotate and test any hot spares in the system.  The main 
> problem with hot spares is that you don't actually know if they work 
> properly until there is a failover...
>
>     -hpa
>

Sorry I don't agree.

Firstly, it causes confusion. If you want a replacement in 90% of cases 
it means that the current drive is defective. If you put the replaced 
drive into the spare pool instead of kicking it out then you have to 
remember (by serial number?) which one it was to actually remove it from 
the system. If you forget to note it down, then you are in serious 
troubles, because if that "spare" then gets caught in another (or the 
same) array needing a recovery, you will have a high probability of 
exotic and unexpected multiple failures situations.

Also, if you are uncertain of the health of your spares, risking your 
array by throwing one into the array is definitely unwise. There are 
other tecniques to test a spare that don't involve risking you array on 
it: you can remove one spare from the spare pool (best if you have 2+ 
spares but can also be done with 1), read/write all of it various times 
as a validation, then re-add it back to the spares pool. Even just 
reading it from beginning to end with dd could be enough and for this 
you don't even have to remove it from the spare pool. And this doesn't 
degrade the array performances, while your suggestion would.

Thirdly, if you really want that (imho unwise) behaviour, it's easy to 
implement from userspace without asing the MD developers to do so: 
monitor the replacement process, as soon as you see it terminating and 
you see the target drive in Failed status, remove and re-add it back as 
a spare. That's it.

  parent reply	other threads:[~2012-11-25 17:59 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
2012-11-25 15:42         ` Piergiorgio Sartor
2012-11-25 18:01       ` Mikael Abrahamsson
2012-11-25 17:59 ` joystick [this message]
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=50B25C77.4000502@shiftmail.org \
    --to=joystick@shiftmail.org \
    --cc=hpa@zytor.com \
    --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).