All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aaron C. de Bruyn" <aaron@darkpixel.com>
To: Andrew Burgess <aab@cichlid.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Moron Destroyed RAID6 Array Superblocks
Date: Fri, 13 Apr 2007 19:59:28 -0700	[thread overview]
Message-ID: <1176519568.7325.3.camel@localhost.localdomain> (raw)
In-Reply-To: <200704081521.l38FLwGU017164@cichlid.com>

Ok--I got moved in to my new place and am back and running on the 'net.
I sat down for a few hours and attempted to write a script to try all
possible combinations of drives...but I have to admit that I'm lost.

I have 8 drives in the array--and I can output every possible
combination of those.  But what the heck would be the logic to output
all combinations of the 8 drives using only 6 at a time?  My head hurts.

-A

On Sun, 2007-04-08 at 08:21 -0700, Andrew Burgess wrote:
> >After reading through the linux-raid archives I have been lead to
> >believe that I can recover my array by doing a --create and listing the
> >7 drives in the exact order I originally created them in.  Is this correct?
> 
> >If so, the kernel upgrade managed to shuffle the drive names around...is
> >there any way I can figure out what order they should be in?
> 
> If you know the old order just boot the old kernel and recreate there
> 
> If you are using kernel rpms, you always want to 'install' new kernels
> and not 'upgrade', that keeps both the old and new kernel available.
> 
> Otherwise, if you pick just 5 for the 7 drives from a raid 6 array
> it seems to me you have 5 factorial combinations = 120. You could write
> a script that tries them all and then tests by trying a read-only mount?
> 
> Good luck. I mashed a 3.5 TB array once by rerunning the lvm
> creation which zeros the first chunk of the resulting device. I was
> used to mdadm not hurting user data when creating. Grrr.
> 
> BTW when you test recreate the array make sure you dont start syncing, thats
> another reason to just use 5 drives.
> 
> HTH
> 
> -
> 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


  reply	other threads:[~2007-04-14  2:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-08 15:21 Moron Destroyed RAID6 Array Superblocks Andrew Burgess
2007-04-14  2:59 ` Aaron C. de Bruyn [this message]
2007-04-14  7:28   ` Corey Hickey
2007-04-14  6:42 ` Aaron C. de Bruyn
  -- strict thread matches above, loose matches on Subject: below --
2007-04-08  4:10 Aaron C. de Bruyn

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=1176519568.7325.3.camel@localhost.localdomain \
    --to=aaron@darkpixel.com \
    --cc=aab@cichlid.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 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.