From: "Karsten Römke" <k.roemke@gmx.de>
To: linux-raid@vger.kernel.org
Subject: Re: Re: misunderstanding of spare and raid devices?
Date: Thu, 30 Jun 2011 15:09:39 +0200 [thread overview]
Message-ID: <4E0C7593.7090304@gmx.de> (raw)
In-Reply-To: <20110630105840.GA27551@cthulhu.home.robinhill.me.uk>
Hello,
I suppose it works now.
After mdadm -w /dev/md0 it starts synching.
md0 : active raid5 sdd5[4] sde5[5](S) sdc5[2] sdb2[1] sda3[0]
13759296 blocks level 5, 64k chunk, algorithm 2 [4/3] [UUU_]
[=>...................] recovery = 6.2% (286656/4586432) finish=0.9min speed=71664K/sec
thanks to both of you.
Karsten
Am 30.06.2011 12:58, schrieb Robin Hill:
> On Thu Jun 30, 2011 at 12:51:37 +0200, Karsten Römke wrote:
>
>> Hello,
>> I'm searching some hours / minutes to create a raid5 device with 4
>> disks and 1 spare:
>> I tried first with the opensuse tool but no success as I want, so I
>> tried mdadm
>>
>> Try:
>> mdadm --create /dev/md0 --level=5 --raid-devices=4 --spare-devices=1
>> /dev/sda3 /dev/sdb2 /dev/sdc5 /dev/sdd5 /dev/sde5
>>
>> leads to
>> Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
>> md0 : active (auto-read-only) raid5 sdd5[5](S) sde5[4](S) sdc5[2] sdb2[1] sda3[0]
>> 13759296 blocks level 5, 64k chunk, algorithm 2 [4/3] [UUU_]
>>
>> 2 spares - I don't understand that.
>>
> That's perfectly normal. The RAID5 array is created in degraded mode,
> then recovered onto the final disk. That way it becomes available for
> use immediately, rather than requiring all the parity to be calculated
> before the array is ready. As it's been started in auto-read-only mode
> (not sure why though) then it hasn't started recovery yet. Running
> "mdadm -w /dev/md0" or mounting the array will kick it into read-write
> mode and start the recovery process.
>
> HTH,
> Robin
--
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
next prev parent reply other threads:[~2011-06-30 13:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 10:51 misunderstanding of spare and raid devices? Karsten Römke
2011-06-30 10:58 ` Robin Hill
2011-06-30 13:09 ` Karsten Römke [this message]
2011-06-30 11:30 ` John Robinson
2011-06-30 12:32 ` Phil Turmel
2011-06-30 12:52 ` misunderstanding of spare and raid devices? - and one question more Karsten Römke
2011-06-30 13:34 ` Phil Turmel
2011-06-30 14:05 ` Karsten Römke
2011-06-30 14:21 ` Karsten Römke
2011-06-30 14:44 ` Phil Turmel
2011-07-02 8:34 ` Karsten Römke
2011-07-02 9:42 ` David Brown
2011-06-30 21:28 ` NeilBrown
2011-07-01 7:23 ` David Brown
2011-07-01 8:50 ` Robin Hill
2011-07-01 10:18 ` David Brown
2011-07-01 11:29 ` Robin Hill
2011-07-01 12:45 ` David Brown
2011-07-01 13:02 ` NeilBrown
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=4E0C7593.7090304@gmx.de \
--to=k.roemke@gmx.de \
--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.