From: "Tuomas Leikola" <tuomas.leikola@gmail.com>
To: tj <lists@jager.no>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid-5 long write wait while reading
Date: Fri, 8 Jun 2007 08:49:28 +0300 [thread overview]
Message-ID: <5b170a7d0706072249i4dbdcb13h826aba07cf31333e@mail.gmail.com> (raw)
In-Reply-To: <466207E3.60307@jager.no>
On 6/3/07, tj <lists@jager.no> wrote:
> >> I just noticed something else. A couple of slow readers where running
> >> on my raid-5 array. Then i started a copy from another local disk to
> >> the array. Then i got the extremely long wait. I noticed something in
> >> iostat:
> >>
> >> avg-cpu: %user %nice %system %iowait %steal %idle
> >> 3.90 0.00 48.05 31.93 0.00 16.12
> >>
> >> Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn
> >> ....
> >> sdg 0.80 25.55 0.00 128 0
> >> sdh 154.89 632.34 0.00 3168 0
> >> sdi 0.20 12.77 0.00 64 0
> >> sdj 0.40 25.55 0.00 128 0
> >> sdk 0.40 25.55 0.00 128 0
> >> sdl 0.80 25.55 0.00 128 0
> >> sdm 0.80 25.55 0.00 128 0
> >> sdn 0.60 23.95 0.00 120 0
> >> md0 199.20 796.81 0.00 3992 0
> >>
> I don't use ext3 i use ReiserFS. ( It seemed like a good idea at the
> time. ) It's mounted with -o noatime.
I've seen similar read patterns on reiserfs-raid5. I have a 6 disk set
with chunk size of 64, and it seems reiserfs's tree is only located on
2 of the disks. It appears reiserfs stores the tree in blocks
dispersed along the entire disk with some interval, and that's not
always optimal for raid.
Another thing you should look into is stripe cache trashing. On
certain kernel versions all raid5 operations go through stripe cache,
which results in a lot of memory copy operations and might present a
bottleneck if there's a lot of random access. If writes occupy the
entire cache, there's no free slots for reads to go through. I might
be wrong here, though, as this is just a guess.
- tuomas
next prev parent reply other threads:[~2007-06-08 5:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 18:03 Raid-5 long write wait while reading Thomas Jager
2007-05-23 6:34 ` Holger Kiehl
2007-05-24 22:23 ` Thomas Jager
2007-05-27 0:06 ` tj
2007-05-28 16:01 ` Bill Davidsen
2007-06-03 0:14 ` tj
2007-06-04 20:31 ` Bill Davidsen
2007-06-07 17:41 ` Bill Davidsen
2007-06-08 5:49 ` Tuomas Leikola [this message]
2007-05-30 6:32 ` Holger Kiehl
2007-05-30 8:00 ` David Greaves
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=5b170a7d0706072249i4dbdcb13h826aba07cf31333e@mail.gmail.com \
--to=tuomas.leikola@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=lists@jager.no \
/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).