From: Ian Pilcher <arequipeno@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: stoppind md from kicking out "bad' drives
Date: Mon, 11 Nov 2013 09:55:29 -0600 [thread overview]
Message-ID: <l5qulc$kaa$1@ger.gmane.org> (raw)
In-Reply-To: <5280870E.6080703@msgid.tls.msk.ru>
On 11/11/2013 01:28 AM, Michael Tokarev wrote:
> The question is: what's missing currently to prevent kicking
> drives from md arrays at all? And I really mean preventing
> _both_ first failed drive (before start of resync) and second
> failed drive?
I'm becoming increasingly convinced that hot-spares are a bad idea,
particularly when you're one failure away from data loss. (I.e. I might
be willing to auto-add a hot-spare after the initial failure in a RAID-6
array, but not after a second failure.)
I much prefer to do a manual recovery, after using a badblocks read-only
test to check all of the component devices for bad sectors. (I also
build my MD arrays out of partitions rather than entire drives to make
this process more manageable.)
--
========================================================================
Ian Pilcher arequipeno@gmail.com
Sent from the cloud -- where it's already tomorrow
========================================================================
next prev parent reply other threads:[~2013-11-11 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 7:28 stoppind md from kicking out "bad' drives Michael Tokarev
2013-11-11 7:41 ` Mikael Abrahamsson
2013-11-11 7:51 ` Michael Tokarev
2013-11-11 7:56 ` Mikael Abrahamsson
2013-11-11 8:05 ` Michael Tokarev
[not found] ` <CAPbD+Re7sVfSawjGFyMZMpU4Oaf3ULTW-UA3eoD_upcgxj3GOg@mail.gmail.com>
2013-11-13 15:45 ` Michael Tokarev
2013-11-11 15:55 ` Ian Pilcher [this message]
2013-11-23 22:05 ` Michael Tokarev
2013-11-24 23:00 ` NeilBrown
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='l5qulc$kaa$1@ger.gmane.org' \
--to=arequipeno@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).