From: Jon Collette <jon@etelos.com>
To: David Greaves <david@dgreaves.com>
Cc: Guy Watkins <linux-raid@watkins-home.com>, linux-raid@vger.kernel.org
Subject: Re: mdadm create to existing raid5
Date: Fri, 13 Jul 2007 11:25:20 -0700 [thread overview]
Message-ID: <4697C390.8000501@etelos.com> (raw)
In-Reply-To: <469754B0.4020104@dgreaves.com>
The mdadm --create with missing instead of a drive is a good idea. Do
you actually say missing or just leave out a drive? However doesn't it
do a sync everytime you create? So wouldn't you run the risk of
corrupting another drive each time? Or does it not sync because of the
saying missing?
To bad I am intent on learning things the hard way.
/etc/mdadm.conf from before I recreated
ARRAY /dev/md2 level=raid5 num-devices=4 spares=1
UUID=4f935928:2b7a1633:71d575d6:dab4d6bc
/etc/mdadm.conf after I recreated
ARRAY /dev/md1 level=raid5 num-devices=4
UUID=81bdd737:901c0a8f:af38cb94:41c4e3da
Well before I heard back from you guys . I noticed this problem and in
my fountain of infinite wisdom I did mdadm --zero-superblock to all my
raid drives and created them again thinking if I got it to look the same
it woud just fix it. Well they do look the same now, I am at work or I
would give you the new mdadm.conf.
I really need to learn patients :(
David Greaves wrote:
> David Greaves wrote:
>> For a simple 4 device array I there are 24 permutations - doable by
>> hand, if you have 5 devices then it's 120, 6 is 720 - getting tricky ;)
>
> Oh, wait, for 4 devices there are 24 permutations - and you need to do
> it 4 times, substituting 'missing' for each device - so 96 trials.
>
> 4320 trials for a 6 device array.
>
> Hmm. I've got a 7 device raid 6 - I think I'll go an make a note of
> how it's put together... <grin>
>
>
> Have a look at this section and the linked script.
> I can't test it until later
>
> http://linux-raid.osdl.org/index.php/RAID_Recovery
>
> http://linux-raid.osdl.org/index.php/Permute_array.pl
>
>
> David
>
>
> -
> 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
prev parent reply other threads:[~2007-07-13 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 21:28 mdadm create to existing raid5 Jon Collette
2007-07-12 23:18 ` Guy Watkins
2007-07-13 8:25 ` David Greaves
2007-07-13 10:32 ` David Greaves
2007-07-13 18:25 ` Jon Collette [this message]
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=4697C390.8000501@etelos.com \
--to=jon@etelos.com \
--cc=david@dgreaves.com \
--cc=linux-raid@vger.kernel.org \
--cc=linux-raid@watkins-home.com \
/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.