From: Neil Brown <neilb@suse.de>
To: Maciej 'Agaran' Pijanka <agaran@pld-linux.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm, raid10, and problem
Date: Tue, 22 May 2007 10:43:34 +1000 [thread overview]
Message-ID: <18002.15542.445123.221297@notabene.brown> (raw)
In-Reply-To: message from Maciej 'Agaran' Pijanka on Sunday May 20
On Sunday May 20, agaran@pld-linux.org wrote:
>
> Hello
>
>
> i was trying to build raid 10 from six devices (currently loops but need
> to check before i try to do same on physical drives).
>
> and mdadm gets bit mad,
>
> mdadm -C -l10 -n6 /dev/loop1 /dev/loop2 /dev/loop3 missing missing
> missing
> produced weird result
What did you expect :-?
> mdadm: RUN_ARRAY failed: Input/output error
> mdadm: stopped /dev/md0
Yes, lots of mdadm's errors are - like this - quite unhelpful. It is
something that I would like to get improved, but it just doesn't get a
high priority.
> -from dmesg:
> md: bind<loop0>
> md: bind<loop1>
> md: bind<loop2>
> md: md0: raid array is not clean -- starting background reconstruction
> raid10: not enough operational mirrors for md0
"not enough" means "you don't have the right drives".
For every level other than raid10, it doesn't matter which drives you
have, it just matter how many there are.
For raid10, you do that to have are set of drives that provides all
blocks. But I just re-used the error message from raid1.
Patches always welcome...
NeilBrown
prev parent reply other threads:[~2007-05-22 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 15:35 mdadm, raid10, and problem Maciej 'Agaran' Pijanka
2007-05-22 0:43 ` Neil Brown [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=18002.15542.445123.221297@notabene.brown \
--to=neilb@suse.de \
--cc=agaran@pld-linux.org \
--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).