From: John Rowe <rowe@excc.ex.ac.uk>
To: Mike Hardy <mhardy@h3c.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Slow reconstruction
Date: Wed, 29 Jun 2005 18:31:08 +0100 [thread overview]
Message-ID: <1120066268.21458.252.camel@volt> (raw)
In-Reply-To: <42C2CEF0.7030108@h3c.com>
Thanks for all the suggestions.
/proc/sys/dev/raid/speed_limit_max had the value "10000", changing it to
200000 didn't make a difference. hdparm looks OK to me:
/dev/hdm1:
Timing buffer-cache reads: 128 MB in 1.19 seconds =107.56 MB/sec
Timing buffered disk reads: 64 MB in 3.13 seconds = 20.45 MB/sec
/dev/hdo1:
Timing buffer-cache reads: 128 MB in 1.17 seconds =109.40 MB/sec
Timing buffered disk reads: 64 MB in 3.85 seconds = 16.62 MB/sec
rsync:/root# hdparm -Tt /dev/hda4
/dev/hda4:
Timing buffer-cache reads: 128 MB in 1.15 seconds =111.30 MB/sec
Timing buffered disk reads: 64 MB in 4.31 seconds = 14.85 MB/sec
/dev/hdc4:
Timing buffer-cache reads: 128 MB in 1.16 seconds =110.34 MB/sec
Timing buffered disk reads: 64 MB in 4.79 seconds = 13.36 MB/sec
/dev/hdi3:
Timing buffer-cache reads: 128 MB in 1.16 seconds =110.34 MB/sec
Timing buffered disk reads: 64 MB in 2.73 seconds = 23.44 MB/sec
/dev/hdk1:
Timing buffer-cache reads: 128 MB in 1.16 seconds =110.34 MB/sec
Timing buffered disk reads: 64 MB in 2.72 seconds = 23.53 MB/sec
DMA is enabled for all six disks.
If it helps, here is my raidtab. I wonder a little about the 64K chunk
size on the stripe but a 128K size on the RAID5. Is this good or bad?
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
chunk-size 64k
persistent-superblock 1
nr-spare-disks 0
device /dev/hda2
raid-disk 0
device /dev/hdc2
raid-disk 1
raiddev /dev/md2
raid-level 0
nr-raid-disks 2
chunk-size 64k
persistent-superblock 1
nr-spare-disks 0
device /dev/hdm1
raid-disk 0
device /dev/hdo1
raid-disk 1
raiddev /dev/md3
raid-level 5
nr-raid-disks 5
chunk-size 128k
parity-algorithm left-symmetric
persistent-superblock 1
nr-spare-disks 0
device /dev/hda4
raid-disk 0
device /dev/hdc4
raid-disk 1
device /dev/hdi3
raid-disk 2
device /dev/hdk1
raid-disk 3
device /dev/md2
raid-disk 4
Comments gratefully received.
John
next prev parent reply other threads:[~2005-06-29 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 16:10 Slow reconstruction John Rowe
2005-06-29 16:40 ` Mike Hardy
2005-06-29 17:31 ` John Rowe [this message]
2005-06-29 17:46 ` seth vidal
2005-06-29 17:49 ` John Rowe
2005-06-29 17:49 ` KELEMEN Peter
2005-06-29 17:52 ` John Rowe
2005-06-29 18:00 ` KELEMEN Peter
2005-06-29 17:54 ` Tyler
2005-06-29 17:32 ` seth vidal
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=1120066268.21458.252.camel@volt \
--to=rowe@excc.ex.ac.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mhardy@h3c.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.