From: Maarten van den Berg <maarten@ultratux.net>
To: linux-raid@vger.kernel.org
Subject: Re: Raid5 Construction Question
Date: Thu, 19 Aug 2004 22:24:06 +0200 [thread overview]
Message-ID: <200408192224.06572.maarten@ultratux.net> (raw)
In-Reply-To: <4124E8F5.1010105@psc.edu>
On Thursday 19 August 2004 19:52, PAulN wrote:
> Guy,
> thanks for the snappy reply! I wish my disks were as fast :)
> I failed to mention that I had been tweaking those proc values. Currently
> they are:
> (root@lcn0:raid)# cat speed_limit_max
> 200000
> (root@lcn0:raid)# cat speed_limit_min
> 10000
>
> If I'm correct, this means that the min speed is 10MB/sec per device.
> I've verified that each device has a seq write speed of about 38MB/sec so
> each should be capable of handling 10,000Kbytes sec. Right after I issue
> a raidstart the speed is pretty good (~30MB/sec) but is just falls until
> it hits
> around 300K.
>
> md0 : active raid5 sdh1[7] sdf1[6] sdg1[5] sde1[4] sdd1[3] sdc1[2]
> sdb1[1] sda1[0]
> 481949184 blocks level 5, 64k chunk, algorithm 2 [7/7] [UUUUUUU]
> [>....................] resync = 2.4% (1936280/80324864)
> finish=4261.4min speed=305K/sec
Something like this happened to me a while ago. The speed is good at start,
then after a certain amount of time starts degrading until very very low,
like 5k/sec. It keeps ever decreasing. Also, the decrease of speed occurred
at exactly the same point every time. After a lot of searching, asking and
bitching the true reason was revealed; one of the disks had problems and
couldn't read/write a part of its surface. Only when I ran dd on it (and saw
the read errors reported) did I realize that.
So if what you are seeing is this ever-decreasing speed, starting at a
specific point, I'd strongly concur with Guy in saying: Test each disk
separately by reading /and or writing its _entire_ surface using the dd
commands suggested. Not using hdparm or benchmarks, but reading the entire
disk(s) as described. The purpose of this is NOT that you get an idea of the
speed, but that you verify that the entire surface is still ok.
Beyond that, I have no suggestions to offer you.
Maarten
next prev parent reply other threads:[~2004-08-19 20:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 17:24 Raid5 Construction Question PAulN
2004-08-19 17:30 ` Guy
2004-08-19 17:52 ` PAulN
2004-08-19 18:17 ` Guy
2004-08-19 18:24 ` PAulN
2004-08-19 18:29 ` Guy
2004-08-19 18:35 ` Gordon Henderson
2004-08-19 20:24 ` Maarten van den Berg [this message]
2004-08-19 20:26 ` Kourosh
2004-08-19 20:39 ` Mike Hardy
2004-08-19 21:50 ` Maarten van den Berg
2004-08-19 21:55 ` Guy
2004-08-19 20:53 ` Guy
2004-08-20 1:21 ` Neil Brown
2004-08-20 1:56 ` Guy
2004-08-20 2:01 ` Neil Brown
2004-08-20 4:53 ` Paul Nowoczynski
2004-08-19 18:32 ` Tim Moore
2004-08-19 20:30 ` Maarten van den Berg
2004-08-23 15:24 ` Tim Moore
2004-08-23 15:27 ` Gordon Henderson
-- strict thread matches above, loose matches on Subject: below --
2004-08-20 5:17 Mike Baynton
2004-08-20 6:52 ` Guy
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=200408192224.06572.maarten@ultratux.net \
--to=maarten@ultratux.net \
--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).