All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Norman White <nwhite@stern.nyu.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: 5 drives lost in an inactive  15 drive raid 6 system due to cable problem - how to recover?
Date: Thu, 9 Sep 2010 07:35:30 +1000	[thread overview]
Message-ID: <20100909073530.1e5da34d@notabene> (raw)
In-Reply-To: <4C87C656.2030405@stern.nyu.edu>

On Wed, 08 Sep 2010 13:22:30 -0400
Norman White <nwhite@stern.nyu.edu> wrote:

> We have a 15 drive addonics array with 3 5 port sata multiplexors, one 
> of the sas cables was knocked out to one of the port multiplexors and now
> mdadm sees 9 drives , a spare, and 5 failed, removed drives (after 
> fixing the cabling problem).
> 
> A mdadm -E on each of the drives, see 5 drives (the ones that were 
> uncabled) as seeing the original  configuration with 14 drives and a 
> spare, while the other 10 drives report
> 9 drives, a spare and 5 failed , removed drives.
> 
> We are very confident that there was no io going on at the time, but are 
> not sure how to proceed.
> 
> One obvious thing to do is to just do a:
> 
> mdadm --assemble --force --assume-clean /dev/md0 sd[b,c, ... , p]
> but we are getting different advice about what force will do in this 
> situation. The last thing we want to do is wipe the array.

What sort of different advice?  From whom?

This should either do exactly what you want, or nothing at all.  I suspect
the former.  To be more confident I would need to see the output of
   mdadm -E /dev/sd[b-p]

NeilBrown


> 
> Another option would be to fiddle with the super blocks with mddump, so 
> that they all see the same 15 drives in the same configuration, and then 
> assemble it.
> 
> Yet another suggestion was to recreate the array configuration and hope 
> that the data wouldn't be touched.
> 
> And even another suggestion is to create the array with one drive 
> missing (so it is degraded and won't rebuild)
> 
> Any pointers on how to proceed would be helpful. Restoring 30TB takes 
> along time.
> 
> Best,
> Norman White
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  parent reply	other threads:[~2010-09-08 21:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 17:22 5 drives lost in an inactive 15 drive raid 6 system due to cable problem - how to recover? Norman White
2010-09-08 18:47 ` Stan Hoeppner
2010-09-08 20:22 ` Mikael Abrahamsson
2010-09-08 21:35 ` Neil Brown [this message]
2010-09-10 15:18   ` Norman White
2010-09-10 17:47     ` Mr. James W. Laferriere
2010-09-10 18:51       ` Norman White
2010-09-10 19:39   ` CoolCold
2010-09-10 21:24     ` Neil Brown

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=20100909073530.1e5da34d@notabene \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=nwhite@stern.nyu.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.