linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Mark Keisler <grimm26@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID10 failure(s)
Date: Tue, 15 Feb 2011 11:57:44 +1100	[thread overview]
Message-ID: <20110215115744.3dd078b0@notabene.brown> (raw)
In-Reply-To: <AANLkTi=5+2WJzg4=7cdWx-1+vUwyLcyHxKishCtX_nOH@mail.gmail.com>

On Mon, 14 Feb 2011 18:49:03 -0600 Mark Keisler <grimm26@gmail.com> wrote:

> Oh, duh, was thinking in 0+1 instead of 10.  I'm still wondering why
> you made mention of "but be really sure that the devices really are
> working before you try this."  If trying to bring the RAID back fails,
> I'm just back to not having access to the data which is where I am now
> :).

If you try reconstructing the array before you are sure you have resolved the
original problem (be it BIOS setting, bad cables, dodgey controller or even a
bad disk drive) then you risk compounding your problems and at least are
likely to waste time.
Sometimes people are in such a hurry to get access to their data that they
cut corners to their detriment.  I don't know if you are such a person, but
I mentioned it anyway just in case.

NeilBrown


  reply	other threads:[~2011-02-15  0:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 16:09 RAID10 failure(s) Mark Keisler
2011-02-14 20:33 ` Mark Keisler
2011-02-14 22:29   ` Stan Hoeppner
     [not found]     ` <AANLkTikyjuUo=X3m5Q6L9x3vXbgV1KC+TfOaLN2z4Keo@mail.gmail.com>
2011-02-15  0:40       ` Stan Hoeppner
2011-02-14 22:48   ` NeilBrown
2011-02-14 23:08     ` Mark Keisler
2011-02-14 23:20       ` NeilBrown
2011-02-15  0:49         ` Mark Keisler
2011-02-15  0:57           ` NeilBrown [this message]
2011-02-15 17:47             ` Mark Keisler
  -- strict thread matches above, loose matches on Subject: below --
2011-02-14 16:07 raid10 failure(s) Mark Keisler

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=20110215115744.3dd078b0@notabene.brown \
    --to=neilb@suse.de \
    --cc=grimm26@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).