linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <lists2009@fnarfbargle.com>
To: joystick <joystick@shiftmail.org>
Cc: NeilBrown <neilb@suse.de>, 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 21:44:47 +0800	[thread overview]
Message-ID: <509A65CF.8020409@fnarfbargle.com> (raw)
In-Reply-To: <509A3029.4050402@shiftmail.org>

On 07/11/12 17:55, joystick wrote:

>
> we still need someone to test the other case, a more common scenario I'd
> say: the disk to be replaced fails during hot-replace

I suspect I can do that by creating some "media errors" using hdparm 
while the replacement is in progress.

I'd have *thought* that the procedure should be to re-direct the read to 
another mirror (it is a raid-10 after all).

>> The test machine is on UPS, so I have not done any testing that
>> involves reboots during a re-sync.
>
> And also this one...
> Best simulation would be unpulling the plug so that disks do not flush
> if you have still time for us, of course :-)

I assume to test that adequately (as in re-assemble an array with a 
replacement in progress) I'd need to upgrade mdadm to the latest git code?

No biggie, just requires a bit more tweaking the initramfs stuff.

The tests thus far have been conducted in spare drive slots in my 
production server. This afternoon I picked up a new motherboard for my 
test box so tomorrow I'll have a dedicated machine to play with.

Debian on SSD, and 10 x 1TB 7200 RPM drives that have been retired from 
active hard service (they have about 22,000 hours on them) and ready as 
a test mule.

If you put together a set of tests you'd like performed I'll be happy to 
run them and see what happens. The machine is on a managed APC PDU (yay 
Gumtree!), so remote power cycling is a lot easier than it used to be 
and I really don't mind hammering the disks with emergency parks or 
excessive cycles.



  reply	other threads:[~2012-11-07 13:44 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
2012-11-07  9:55     ` joystick
2012-11-07 13:44       ` Brad Campbell [this message]
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=509A65CF.8020409@fnarfbargle.com \
    --to=lists2009@fnarfbargle.com \
    --cc=joystick@shiftmail.org \
    --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).