All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: "Peckins, Steven E" <speckins@illinois.edu>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: RAID6 recovery with 6/9 drives out-of-sync
Date: Tue, 31 May 2016 15:19:12 -0400	[thread overview]
Message-ID: <574DE3B0.8000409@turmel.org> (raw)
In-Reply-To: <C50C72C6-FC75-4863-B743-F63F09AF93B0@illinois.edu>

On 05/30/2016 10:43 PM, Peckins, Steven E wrote:
> 
> I have a system with a 9+1 disk RAID6 array that has "3 drives and 1 spare - not enough to start the array."  The metadata version is 1.1; mdadm version is v3.3.
> 
> The component devices in the array are supposed to be multipath devices (dm-multipath), but for some reason, when the server was restarted, md grabbed both dm-* components and raw devices.  I *think* that this is what caused the problem.

Quite possible.  You probably need a DEVICES clause in your mdadm.conf
to exclude the raw devices from the arrays.


> I'm seeking advice on how to proceed at this point.  If more information is required, please ask.

Hmmm.  The partial success on mdadm --force suggests trying that again.
 Possible with --force twice on the command line.

Forced assembly is precisely what you need -- don't despair and attempt
anything else.

Do review /proc/mdstat before each assembly attempt to make sure nothing
is partially assembled with those devices or the underlying raw devices.

Phil


  reply	other threads:[~2016-05-31 19:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31  2:43 RAID6 recovery with 6/9 drives out-of-sync Peckins, Steven E
2016-05-31 19:19 ` Phil Turmel [this message]
2016-06-01 11:32   ` Peckins, Steven E
2016-06-01 12:06     ` Phil Turmel
2016-06-01 13:16       ` Peckins, Steven E
2016-06-01 13:22         ` Phil Turmel

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=574DE3B0.8000409@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=speckins@illinois.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.