From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: RAID5 initial rebuild slow, 2.6.16-rc4
Date: Thu, 2 Mar 2006 16:48:21 +0000 [thread overview]
Message-ID: <200603021648.21465.s0348365@sms.ed.ac.uk> (raw)
Hi Neil,
I recently purchased two SATA2 Western Digital WD2500KS (250GB) HDs to add to
a pair of Maxtor DiamondMax 10's (200GB). I planned to initialise two 100GB
RAID5 arrays spanning all four drives (the remaining 2x50GB on the new HDs is
currently used for booting).
All the drives are connected to the same controller. I'm running mdadm 2.3.1,
which is the latest version I believe. I created the array with the following
command:
mdadm --create /dev/md1 --auto=yes --chunk=64 --level=5
--raid-devices=4 /dev/sda3 /dev/sdb3 /dev/sdc2 /dev/sdd2
A few seconds later the array completed and I got the following
in /proc/mdstat:
[root] 16:45 [~] cat /proc/mdstat
Personalities : [raid0] [raid5] [raid4] [multipath]
md2 : active raid0 sdb1[1] sda1[0]
195318016 blocks 32k chunks
md1 : active raid5 sdd2[4] sdc2[2] sdb3[1] sda3[0]
298736448 blocks level 5, 64k chunk, algorithm 2 [4/3] [UUU_]
[>....................] recovery = 0.5% (501376/99578816)
finish=1646.2min speed=1000K/sec
I've not yet attempted to put a filesystem on the device, because I planned to
wait until the (presumably pointless) recovery process completed. However,
this rebuild seems to be extremely slow (the speed never exceeds the
"minimum" recovery speed). CPU usage is almost nill.
This machine is an Athlon64 X2 3800+, with 2GB RAM, running an x86_64 kernel.
Is there any reason for this poor performance?
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next reply other threads:[~2006-03-02 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 16:48 Alistair John Strachan [this message]
2006-03-02 16:57 ` Alistair John Strachan
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=200603021648.21465.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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
all inboxes | Powered by JetHome®