LKML Archive on
help / color / mirror / Atom feed
From: Jason Rainforest <>
To: Justin Piszcz <>
Subject: Re: 2.6.20: stripe_cache_size goes boom with 32mb
Date: Fri, 23 Feb 2007 22:41:00 +1000	[thread overview]
Message-ID: <1172234460.4419.7.camel@merlin> (raw)
In-Reply-To: <Pine.LNX.4.64.0702230640430.3781@p34.internal.lan>

Hi Justin,

I'm not a RAID or kernel developer, but .. do you have enough RAM to
support a 32mb stripe_cache_size?! Here on my 7*250Gb SW RAID5 array,
decreasing a stripe_cache_size of 8192 to 4096 frees up no less than
120mb of RAM. Using that as a calculation tool, a 32mb stripe_cache_size
would require approximately 960mb of RAM! My RAID box only has 1Gb of
RAM, so I'm not game to test such a thing. Others on these lists would
definitely have a good idea on what's happening :-)


On Fri, 2007-02-23 at 06:41 -0500, Justin Piszcz wrote:
> Each of these are averaged over three runs with 6 SATA disks in a SW RAID 
> 5 configuration:
> (dd if=/dev/zero of=file_1 bs=1M count=2000)
> 128k_stripe: 69.2MB/s
> 256k_stripe: 105.3MB/s
> 512k_stripe: 142.0MB/s
> 1024k_stripe: 144.6MB/s
> 2048k_stripe: 208.3MB/s
> 4096k_stripe: 223.6MB/s
> 8192k_stripe: 226.0MB/s
> 16384k_stripe: 215.0MB/s
> When I tried a 32768k stripe, this happened:
> p34:~# echo 32768 > /sys/block/md4/md/stripe_cache_size
> Connection to p34 closed
> I was able to Alt-SysRQ+b but I could not access the console/X/etc, it 
> appeared to be frozen.
> FYI.
> Justin.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to
> More majordomo info at

  reply	other threads:[~2007-02-23 12:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 11:41 Justin Piszcz
2007-02-23 12:41 ` Jason Rainforest [this message]
2007-02-23 12:42   ` Justin Piszcz
2007-02-23 19:11     ` Dan Williams
2007-02-23 13:11 ` Jan Engelhardt

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1172234460.4419.7.camel@merlin \ \ \ \ \
    --subject='Re: 2.6.20: stripe_cache_size goes boom with 32mb' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).