From: "Dan Williams" <dan.j.williams@intel.com>
To: Neil Brown <neilb@suse.de>
Cc: Rainer Fuegenstein <rfu@kaneda.iguw.tuwien.ac.at>,
linux-raid@vger.kernel.org
Subject: Re: is this raid5 OK ?
Date: Thu, 29 Mar 2007 22:51:28 -0700 [thread overview]
Message-ID: <e9c3a7c20703292251v7cbbda6eg212e0bb6246f62ae@mail.gmail.com> (raw)
In-Reply-To: <17932.22575.558925.535963@notabene.brown>
On 3/29/07, Neil Brown <neilb@suse.de> wrote:
> On Thursday March 29, rfu@kaneda.iguw.tuwien.ac.at wrote:
> > hi,
> >
> > I manually created my first raid5 on 4 400 GB pata harddisks:
> >
> > [root@server ~]# mdadm --create --verbose /dev/md0 --level=5 --raid-devices=4 --spare-devices=0 /dev/hde1 /dev/hdf1 /dev/hdg1 /dev/hdh1
> > mdadm: layout defaults to left-symmetric
> > mdadm: chunk size defaults to 64K
> > mdadm: size set to 390708736K
> > mdadm: array /dev/md0 started.
> >
> > but, mdstat shows:
> >
> > [root@server ~]# cat /proc/mdstat
> > Personalities : [raid6] [raid5] [raid4]
> > md0 : active raid5 hdh1[4] hdg1[2] hdf1[1] hde1[0]
> > 1172126208 blocks level 5, 64k chunk, algorithm 2 [4/3] [UUU_]
> >
> > unused devices: <none>
> >
> > I'm surprised to see that there's one "failed" device [UUU_] ?
> > shouldn't it read [UUUU] ?
>
> It should read "UUU_" at first while building the 4th drive
> (rebuilding a missing drive is faster that calculating and writing all
> the parity blocks). But it doesn't seem to be doing that.
>
> What kernel version? Try the latest 2.6.x.y in that series.
>
I have seen something similar with older versions of mdadm when
specifying all the member drives at once. Does the following kick
things into action?
mdadm --create /dev/md0 -n 4 -l 5 /dev/hd[efg]1 missing
mdadm --add /dev/md0 /dev/hdh1
--
Dan
next prev parent reply other threads:[~2007-03-30 5:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 17:38 is this raid5 OK ? Rainer Fuegenstein
2007-03-29 22:35 ` Justin Piszcz
2007-03-30 0:22 ` Neil Brown
2007-03-30 5:51 ` Dan Williams [this message]
2007-03-30 11:43 ` Rainer Fuegenstein
2007-03-30 16:28 ` Bill Davidsen
2007-03-30 18:23 ` Rainer Fuegenstein
2007-03-30 20:58 ` Justin Piszcz
2007-03-31 1:00 ` Bill Davidsen
2007-03-31 0:59 ` Bill Davidsen
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=e9c3a7c20703292251v7cbbda6eg212e0bb6246f62ae@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=rfu@kaneda.iguw.tuwien.ac.at \
/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).