linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: PAulN <pauln@psc.edu>
To: Guy <bugzilla@watkins-home.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid5 Construction Question
Date: Thu, 19 Aug 2004 13:52:53 -0400	[thread overview]
Message-ID: <4124E8F5.1010105@psc.edu> (raw)
In-Reply-To: <200408191730.i7JHUd313659@watkins-home.com>

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

In the docs I saw that "reconstruction" is possible with raidhotadd but 
I didn't
see anything about initialization.   So am I "screwed" until the resync 
is fixed?  I was depeding
on the disks to do some filesystem testing but maybe I'll have to wait a 
few days.. 
Thanks,
Paul


Guy wrote:

>In short... Issue this command:
>echo 100000 > /proc/sys/dev/raid/speed_limit_max
>
>If it does not help issue this command and send the results:
>cat /proc/mdstat
>
>Details below.
>
>These are related to throttling:
>/proc/sys/dev/raid/speed_limit_max
>/proc/sys/dev/raid/speed_limit_min
>
>Do "man md" for more info.
>
>The speed limits are per device, not per array.
>Make sure the max is large enough the permit your disks to go as fast as
>they can.  I use 100000 (100,000K bytes/second).  My disks are not that
>fast, and having too large of a number does not hurt.
>At least as a test, set the min to the same value as max.
>
>I use these commands when I want to change by hand:
>cat /proc/sys/dev/raid/speed_limit_max
>cat /proc/sys/dev/raid/speed_limit_min
>
>echo 100000 > /proc/sys/dev/raid/speed_limit_max
>echo 1000 > /proc/sys/dev/raid/speed_limit_min
>
>Guy
>
>-----Original Message-----
>From: linux-raid-owner@vger.kernel.org
>[mailto:linux-raid-owner@vger.kernel.org] On Behalf Of PAulN
>Sent: Thursday, August 19, 2004 1:25 PM
>To: linux-raid@vger.kernel.org
>Subject: Raid5 Construction Question
>
>Hi,
>So I have a raid 5 which is around ~1TB and the problem I've been having 
>is that
>the resync rate is really bad.  This is understandable given that the 
>raid5 has not
>been initialized.  Does anyone know a way for me to initialize my raid5 
>before I use it so
>that the resync process doesn't run for 3 days?
>thanks
>paul
>
>
>Config:
>-------------------------------------------------
>raiddev             /dev/md0
>raid-level                  5
>nr-raid-disks               7
>nr-spare-disks              1
>chunk-size                  64k
>persistent-superblock       1
>parity-algorithm        left-symmetric
>    device          /dev/sda1
>    raid-disk     0
>    device          /dev/sdb1
>    raid-disk     1
>    device          /dev/sdc1
>    raid-disk     2
>    device          /dev/sdd1
>    raid-disk     3
>    device          /dev/sde1
>    raid-disk     4
>    device          /dev/sdg1
>    raid-disk     5
>    device          /dev/sdf1
>    raid-disk    6
>    device          /dev/sdh1
>    spare-disk     0
>----------------------------------------
>
>-
>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
>  
>



  reply	other threads:[~2004-08-19 17:52 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 [this message]
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
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=4124E8F5.1010105@psc.edu \
    --to=pauln@psc.edu \
    --cc=bugzilla@watkins-home.com \
    --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).