linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Raz <raziebe@gmail.com>,
	jnelson-linux-raid@jamponi.net, linux-raid@vger.kernel.org
Subject: Re: stripe_cache_size and performance [BUG with =64kb]
Date: Mon, 25 Jun 2007 16:36:25 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706251636180.6115@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0706251548510.3920@p34.internal.lan>



On Mon, 25 Jun 2007, Justin Piszcz wrote:

>
>
> On Mon, 25 Jun 2007, Justin Piszcz wrote:
>
>> 
>> 
>> On Mon, 25 Jun 2007, Justin Piszcz wrote:
>> 
>>> 
>>> 
>>> On Mon, 25 Jun 2007, Bill Davidsen wrote:
>>> 
>>>> Justin Piszcz wrote:
>>>>> I have found a 16MB stripe_cache_size results in optimal performance 
>>>>> after testing many many values :)
>>>> 
>>>> We have discussed this before, my experience has been that after 8 x 
>>>> stripe size the performance gains hit diminishing returns, particularly 
>>>> for typical write instead of big aligned blocks, possibly with O_DIRECT. 
>>>> I would suggest that as a target even on a low memory machine.
>>>> 
>>>> Do your tests show similar? I was only able to test three and four drive 
>>>> setups using dedicated drives.
>>>> 
>>>> -- 
>>>> bill davidsen <davidsen@tmr.com>
>>>> CTO TMR Associates, Inc
>>>> Doing interesting things with small computers since 1979
>>>> 
>>>> -
>>>> 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
>>>> 
>>> 
>>> Running test with 10 RAPTOR 150 hard drives, expect it to take awhile 
>>> until I get the results, avg them etc. :)
>>> 
>>> 128k,256k,512k,1024k,2048k,4096k,8192k,16384k
>>> 
>>> Justin.
>>> 
>> 
>> Definitely a kernel bug, I set it to 64kb and it stayed in D-state until I 
>> ran alt-sysrq-b.
>> 
>> Pretty nasty!
>> 
>> Justin.
>> 
>
> Ack, help??
>
> [   64.032895] Starting XFS recovery on filesystem: md3 (logdev: internal)
> [   66.210602] XFS: xlog_recover_process_data: bad clientid
> [   66.210656] XFS: log mount/recovery failed: error 5
> [   66.210709] XFS: log mount failed
>
> After I ran 64kb it killed my RAID!
> -
> 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
>

Yeah, I won't be trying that anymore :P

p34:/r1# find lost+found/|wc
     157     157    3369
p34:/r1# du -sh lost+found/
166G    lost+found/
p34:/r1#


  reply	other threads:[~2007-06-25 20:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21 18:28 stripe_cache_size and performance Jon Nelson
2007-06-21 19:42 ` Raz
2007-06-21 23:09   ` Jon Nelson
2007-06-22 15:01     ` Raz
2007-06-22 15:10       ` Justin Piszcz
2007-06-25 16:48         ` Bill Davidsen
2007-06-25 17:00           ` Justin Piszcz
2007-06-25 18:20             ` Justin Piszcz
2007-06-25 18:21               ` Justin Piszcz
2007-06-25 18:42           ` Justin Piszcz
2007-06-25 19:48             ` stripe_cache_size and performance [BUG with =64kb] Justin Piszcz
2007-06-25 19:49               ` Justin Piszcz
2007-06-25 20:36                 ` Justin Piszcz [this message]
2007-06-25 20:42                   ` Justin Piszcz
2007-06-25 22:12     ` stripe_cache_size and performance Jon Nelson
2007-06-25 22:19       ` Dan Williams
2007-06-25 23:23         ` Jon Nelson
2007-06-25 22:21       ` Justin Piszcz
2007-06-26 13:58         ` Jon Nelson
2007-06-26 14:00           ` Justin Piszcz
2007-06-26 14:16             ` Jon Nelson
2007-06-26 14:37               ` Justin Piszcz
2007-06-26 15:22                 ` Jon Nelson
2007-06-26 15:54                   ` Justin Piszcz

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=Pine.LNX.4.64.0706251636180.6115@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=davidsen@tmr.com \
    --cc=jnelson-linux-raid@jamponi.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=raziebe@gmail.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 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).