All of
 help / color / mirror / Atom feed
From: Bill Davidsen <>
To: "Raz Ben-Jehuda(caro)" <>
Cc: Eyal Lebedinsky <>,
	linux-raid list <>
Subject: Re: slow 'check'
Date: Wed, 14 Feb 2007 11:41:09 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Raz Ben-Jehuda(caro) wrote:
> I suggest you test all drives concurrently with dd.
> load dd on sda , then sdb slowly one after the other and
> see whether the throughput degrades. use iostat.
> furtheremore, dd is not the measure for random access.
AFAIK 'check' does no do random access, which was the original question. 
My figures are related only to that.

For random access, read should access only one drive unless there's an 
error, and write two, data and updated parity. I don't have the tool I 
want to measure this properly, perhaps later this week I'll generate one.
> On 2/10/07, Bill Davidsen <> wrote:
>> Wait, let's say that we have three drives and 1m chunk size. So we read
>> 1M here, 1M there, and 1M somewhere else, and get 2M data and 1M parity
>> which we check. With five we would read 4M data and 1M parity, but have
>> 4M checked. The end case is that for each stripe we read N*chunk bytes
>> and verify (N-1)*chunk. In fact the data is (N-1)/N of the stripe, and
>> the percentage gets higher (not lower) as you add drives. I see no
>> reason why more drives would be slower, a higher percentage of the bytes
>> read are data.
>> That doesn't mean that you can't run out of Bus bandwidth, but number of
>> drives is not obviously the issue. 

bill davidsen <>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979

      reply	other threads:[~2007-02-14 16:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-10  5:41 slow 'check' Eyal Lebedinsky
2007-02-10  7:41 ` Raz Ben-Jehuda(caro)
2007-02-10  9:57   ` Eyal Lebedinsky
2007-02-10 20:18   ` Bill Davidsen
2007-02-10  9:25 ` Justin Piszcz
2007-02-10 10:15   ` Eyal Lebedinsky
2007-02-10 10:23     ` Justin Piszcz
2007-02-10 20:35       ` Bill Davidsen
2007-02-11  9:30         ` Raz Ben-Jehuda(caro)
2007-02-14 16:41           ` Bill Davidsen [this message]

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 \ \ \ \ \ \

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