All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Scobie <richard@sauce.co.nz>
To: linux-raid@vger.kernel.org
Subject: Re: raid5 grow reshaping speed is unchangeable
Date: Fri, 28 Dec 2007 16:13:23 +1300	[thread overview]
Message-ID: <477469D3.2030202@sauce.co.nz> (raw)
In-Reply-To: <47744926.6010808@tmr.com>


> Cody Yellan wrote:
>> I had a 4x500GB SATA2 array, md0.  I added one 500GB drive and
>> reshaping began at ~2500K/sec.  Changing
>> /proc/sys/dev/raid/speed_limit_m{in,ax} or
>> /sys/block/md0/md/sync_speed_m{in,ax} had no effect.  I shut down all
>> unnecessary services and the array is offline (not mounted).  I have
>> read that the throttling code is "fragile" (esp. with regard to
>> raid5) but does this make sense?  I will wait (in)patiently for it to
>> finish, but I do wonder why the configuration parameters have no
>> effect.  This is a dual quad 2GHz Xeon machine with 8GB of memory
>> running RHEL5.  Is this the maximum speed?

Are you running a non-standard /sys/block/md5/md/stripe_cache_size?

I found when running a kernel of about that vintage on FC6 (which I 
guess became RHEL5), that with a stripe_cache_size of 16384, resyncs 
dropped down to about the speed you are seeing.

This changed back to more normal speeds with a later kernel, but I do 
not recall which.

Regards,

Richard

  reply	other threads:[~2007-12-28  3:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-27  5:22 raid5 grow reshaping speed is unchangeable Cody Yellan
2007-12-27 22:10 ` Nagilum
2007-12-28  0:53 ` Bill Davidsen
2007-12-28  3:13   ` Richard Scobie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-12-27  7:46 Cody Yellan
2007-12-28  0:57 ` Bill Davidsen
2007-12-28 19:21 Cody Yellan
2007-12-29  4:38 ` Richard Scobie
2007-12-29  0:52 Cody Yellan

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=477469D3.2030202@sauce.co.nz \
    --to=richard@sauce.co.nz \
    --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.