From: Tommy Apel Hansen <tommyapeldk@gmail.com>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: Suggestion for hot-replace
Date: Sun, 25 Nov 2012 13:31:06 +0100 [thread overview]
Message-ID: <1759500.SiuUO4mi0r@workstation-home> (raw)
In-Reply-To: <20121125101306.GA2373@lazy.lzy>
On Sunday 25 November 2012 11:13:06 Piergiorgio Sartor wrote:
> On Sat, Nov 24, 2012 at 10:37:49PM -0800, 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...
>
> I go for this one.
>
> Actually, this was also my original thinking for
> the "proactive replacement".
>
> The only thing that, in addition, should be done,
> is to keep the spare in sleep mode until needed
> (either for hot replacement or for real replacement).
>
> bye,
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.
/Tommy
next prev parent reply other threads:[~2012-11-25 12:31 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 [this message]
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
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=1759500.SiuUO4mi0r@workstation-home \
--to=tommyapeldk@gmail.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).