From: Sebastian Kuzminsky <seb@highlab.com>
To: linux-raid@vger.kernel.org
Subject: Re: Raid sync observations
Date: Tue, 20 Dec 2005 11:14:21 -0700 [thread overview]
Message-ID: <E1Eom0D-0008NR-W7@highlab.com> (raw)
In-Reply-To: <E1Eol86-0008Ju-3J@highlab.com>
Sebastian Kuzminsky <seb@highlab.com> wrote:
> Question 1: Why didnt the raid sync I/O show up with vmstat?
>
> Question 2: Why was it limited to 17 MB per second? The maximum was
> left at the default, 200 MB/s. The min was also at the default, 1 MB/s.
> I get 60 MB/s per disk with "hdparm -tT" (that's using one disk at a time,
> but still). The checksumming code does > 3 GB/s.
Some more info... vmstat doesnt see it, but "iostat -m" does:
avg-cpu: %user %nice %system %iowait %steal %idle
0.00 0.00 3.96 0.00 0.00 96.04
Device: tps MB_read/s MB_wrtn/s MB_read MB_wrtn
hda 0.00 0.00 0.00 0 0
hde 0.00 0.00 0.00 0 0
hdg 0.00 0.00 0.00 0 0
hdi 0.00 0.00 0.00 0 0
hdk 0.00 0.00 0.00 0 0
sda 201.00 18.06 8.56 18 8
sdb 184.00 18.06 8.62 18 8
sdc 209.00 18.06 8.59 18 8
sdd 151.00 17.16 9.00 17 9
md0 0.00 0.00 0.00 0 0
md1 0.00 0.00 0.00 0 0
hda is the system disk, hd[egik] are PATA disks that make up md0, and
sd[abcd] are SATA disks that make up md1. md0 is idle, md1 is syncing.
This all makes more sense now - it's only getting 18 MB/s because it's
spending all that time writing.
But wait, why is it only writing half as much as it reads? This is a
4-disk RAID-6, as I understand it, it should read 2 strips and write 2
strips per stripe.
--
Sebastian Kuzminsky
next prev parent reply other threads:[~2005-12-20 18:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 17:18 Raid sync observations Sebastian Kuzminsky
2005-12-20 18:14 ` Sebastian Kuzminsky [this message]
2005-12-20 21:27 ` Neil Brown
2005-12-20 21:33 ` Sebastian Kuzminsky
2005-12-21 1:55 ` Christopher Smith
2005-12-21 11:49 ` Andy Smith
2005-12-21 17:02 ` Sebastian Kuzminsky
2005-12-21 17:13 ` Gordon Henderson
2006-01-08 18:18 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2005-12-20 18:27 Andrew Burgess
2005-12-20 19:13 ` Sebastian Kuzminsky
2005-12-20 22:09 Jeff Breidenbach
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=E1Eom0D-0008NR-W7@highlab.com \
--to=seb@highlab.com \
--cc=linux-raid@vger.kernel.org \
/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).