linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <lists2009@fnarfbargle.com>
To: NeilBrown <neilb@suse.de>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, linux-raid@vger.kernel.org
Subject: Re: is "replaceable" in 3.2 considered stable
Date: Wed, 07 Nov 2012 09:42:03 +0800	[thread overview]
Message-ID: <5099BC6B.7030500@fnarfbargle.com> (raw)
In-Reply-To: <20121105162227.7bc5c103@notabene.brown>

On 05/11/12 13:22, NeilBrown wrote:

>
> Try it.  If it works for you, we can be more confident that it is stable :-)
>
> Seriously I think it is safe to try but I won't promise that nothing will go
> wrong.  I do promise that if something goes wrong (which is fairly unlikely),
> I'll do my best to help you fix it, and think it is extremely unlikely that
> the experiment will cause data loss.

I have a test system set up at the moment with a RAID10 n,2 across 6 1TB 
drives + 2 spares.

I've run several hot-replace tests using 3.6.2 and found it works as 
advertised.

I also have two drives with hard write errors (excellent for failure 
testing), and trying to replace a drive with one that contains a write 
error fails the replace as you would expect.

The test machine is on UPS, so I have not done any testing that involves 
reboots during a re-sync.


  parent reply	other threads:[~2012-11-07  1:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05  4:51 is "replaceable" in 3.2 considered stable Mikael Abrahamsson
2012-11-05  5:22 ` NeilBrown
2012-11-05  8:11   ` Mikael Abrahamsson
2012-11-05  8:42     ` NeilBrown
2012-11-05  8:46       ` Mikael Abrahamsson
2012-11-05 10:53         ` NeilBrown
2012-11-05 10:56           ` Mikael Abrahamsson
2012-11-07  1:42   ` Brad Campbell [this message]
2012-11-07  9:55     ` joystick
2012-11-07 13:44       ` Brad Campbell
2012-11-07 18:08         ` joystick

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=5099BC6B.7030500@fnarfbargle.com \
    --to=lists2009@fnarfbargle.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=swmike@swm.pp.se \
    /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).