All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Al Boldi <a1426z@gawab.com>,
	xfs@oss.sgi.com, linux-raid@vger.kernel.org,
	Alan Piszcz <ap@solarrain.com>
Subject: Re: Linux Software RAID 5 + XFS Multi-Benchmarks / 10 Raptors Again
Date: Fri, 18 Jan 2008 10:24:44 -0500	[thread overview]
Message-ID: <4790C4BC.90802@tmr.com> (raw)
In-Reply-To: <alpine.DEB.0.999999.0801161754180.4552@p34.internal.lan>

Justin Piszcz wrote:
>
>
> On Thu, 17 Jan 2008, Al Boldi wrote:
>
>> Justin Piszcz wrote:
>>> On Wed, 16 Jan 2008, Al Boldi wrote:
>>>>> Also, can you retest using dd with different block-sizes?
>>>
>>> I can do this, moment..
>>>
>>>
>>> I know about oflag=direct but I choose to use dd with sync and 
>>> measure the
>>> total time it takes.
>>> /usr/bin/time -f %E -o ~/$i=chunk.txt bash -c 'dd if=/dev/zero
>>> of=/r1/bigfile bs=1M count=10240; sync'
>>>
>>> So I was asked on the mailing list to test dd with various chunk sizes,
>>> here is the length of time it took
>>> to write 10 GiB and sync per each chunk size:
>>>
>>> 4=chunk.txt:0:25.46
>>> 8=chunk.txt:0:25.63
>>> 16=chunk.txt:0:25.26
>>> 32=chunk.txt:0:25.08
>>> 64=chunk.txt:0:25.55
>>> 128=chunk.txt:0:25.26
>>> 256=chunk.txt:0:24.72
>>> 512=chunk.txt:0:24.71
>>> 1024=chunk.txt:0:25.40
>>> 2048=chunk.txt:0:25.71
>>> 4096=chunk.txt:0:27.18
>>> 8192=chunk.txt:0:29.00
>>> 16384=chunk.txt:0:31.43
>>> 32768=chunk.txt:0:50.11
>>> 65536=chunk.txt:2:20.80
>>
>> What do you get with bs=512,1k,2k,4k,8k,16k...
>>
>>
>> Thanks!
>>
>> -- 
>> Al
>>
>> -
>> 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
>>
>
> root      4621  0.0  0.0  12404   760 pts/2    D+   17:53   0:00 mdadm 
> -S /dev/md3
> root      4664  0.0  0.0   4264   728 pts/5    S+   17:54   0:00 grep D
>
> Tried to stop it when it was re-syncing, DEADLOCK :(
>
> [  305.464904] md: md3 still in use.
> [  314.595281] md: md_do_sync() got signal ... exiting
>
> Anyhow, done testing, time to move data back on if I can kill the 
> resync process w/out deadlock.

So does that indicate that there is still a deadlock issue, or that you 
don't have the latest patches installed?

-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 



  reply	other threads:[~2008-01-18 15:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 16:13 Linux Software RAID 5 + XFS Multi-Benchmarks / 10 Raptors Again Justin Piszcz
2008-01-16 16:55 ` Justin Piszcz
2008-01-16 17:27 ` Al Boldi
2008-01-16 18:02   ` Justin Piszcz
2008-01-16 21:19     ` Al Boldi
2008-01-16 22:53       ` Justin Piszcz
2008-01-16 22:55       ` Justin Piszcz
2008-01-18 15:24         ` Bill Davidsen [this message]
2008-01-18 15:28           ` Justin Piszcz
2008-01-16 18:09 ` Greg Cormier
2008-01-16 18:19   ` Justin Piszcz
2008-02-19 21:48     ` Peter Grandi
2008-01-18 15:35 ` Greg Cormier
2008-01-18 15:39   ` Justin Piszcz
2008-01-18 15:43     ` Greg Cormier
2008-01-18 15:58       ` 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=4790C4BC.90802@tmr.com \
    --to=davidsen@tmr.com \
    --cc=a1426z@gawab.com \
    --cc=ap@solarrain.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=xfs@oss.sgi.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 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.