All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Wagoner <rswagoner@gmail.com>
To: David Lethe <david@santools.com>
Cc: Bill Davidsen <davidsen@tmr.com>,
	Alain Williams <addw@phcomp.co.uk>,
	linux-raid@vger.kernel.org
Subject: Re: High IO Wait with RAID 1
Date: Fri, 13 Mar 2009 13:29:53 -0500	[thread overview]
Message-ID: <7d86ddb90903131129k2fa7d98ah636320c9a3b78259@mail.gmail.com> (raw)
In-Reply-To: <407601c9a405$d3d76b6a$e90df40a@exchange.rackspace.com>

The card has the latest non RAID firmware loaded on it. The LSI 1068
model comes default from Supermicro with the non RAID firmware. It
only has an ARM processor capable of RAID 0 or 1 if you load the RAID
firmware.

The other system with the onboard ICH controller exhibits the same
symptoms so I think my card is configured correctly. The interesting
part of this is I can kick off a resync on all three RAID volumes and
the system load and io wait is low. The rebuild rate is 85M/s for the
RAID 5 volume and 65M/s for the RAID 1 volumes, which is the max each
individual drive can do.

Ryan

On Fri, Mar 13, 2009 at 1:02 PM, David Lethe <david@santools.com> wrote:
> -----Original Message-----
>
> From:  "Ryan Wagoner" <rswagoner@gmail.com>
> Subj:  Re: High IO Wait with RAID 1
> Date:  Fri Mar 13, 2009 12:45 pm
> Size:  2K
> To:  "Bill Davidsen" <davidsen@tmr.com>
> cc:  "Alain Williams" <addw@phcomp.co.uk>; "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
>
> Yeah I understand the basics to RAID and the effect cache has on
> performance. It just seems that RAID 1 should offer better write
> performance than a 3 drive RAID 5 array. However I haven't run the
> numbers so I could be wrong.
>
> It could be just that I expect too much from RAID 1. I'm debating
> about reloading the box with RAID 10 across 160GB of the 4 drives
> (160GB and 320GB) and a mirror on the remaining space. In theory this
> should gain me write performance.
>
> Thanks,
> Ryan
>
> On Fri, Mar 13, 2009 at 11:22 AM, Bill Davidsen <davidsen@tmr.com> wrote:
>> Ryan Wagoner wrote:
>>>
>>> I'm glad I'm not the only one experiencing the issue. Luckily the
>>> issues on both my systems aren't as bad. I don't have any errors
>>> showing in /var/log/messages on either system. I've been trying to
>>> track down this issue for about a year now. I just recently my the
>>> connection with RAID 1 and mdadm when copying data on the second
>>> system.
>>>
>>> Unfortunately it looks like the fix is to avoid software RAID 1. I
>>> prefer software RAID over hardware RAID on my home systems for the
>>> flexibility it offers, especially since I can easily move the disks
>>> between systems in the case of hardware failure.
>>>
>>> If I can find time to migrate the VMs, which run my web sites and
>>> email to another machine, I'll reinstall the one system utilizing RAID
>>> 1 on the LSI controller. It doesn't support RAID 5 so I'm hoping I can
>>> just pass the remaining disks through.
>>>
>
> FYi - you can potentially get  a big performance penalty when running a LSI raid card in jbod mode.  The impact varies depending on a lot of things ..   Try loading the jbod fimware on the card if it supports this and re run benchmarks
>
> david
>
>
--
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

  reply	other threads:[~2009-03-13 18:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13 18:02 High IO Wait with RAID 1 David Lethe
2009-03-13 18:29 ` Ryan Wagoner [this message]
2009-03-13 22:10   ` David Rees
  -- strict thread matches above, loose matches on Subject: below --
2009-03-12 23:46 Ryan Wagoner
2009-03-13  0:48 ` Alain Williams
2009-03-13  3:21   ` Ryan Wagoner
2009-03-13  9:39     ` Robin Hill
2009-03-13 10:17     ` Alain Williams
2009-03-13 16:22     ` Bill Davidsen
2009-03-13 17:42       ` Ryan Wagoner
2009-03-13 18:37         ` David Rees
2009-03-13 18:42   ` David Rees
2009-03-13 14:48 ` John Robinson

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=7d86ddb90903131129k2fa7d98ah636320c9a3b78259@mail.gmail.com \
    --to=rswagoner@gmail.com \
    --cc=addw@phcomp.co.uk \
    --cc=david@santools.com \
    --cc=davidsen@tmr.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 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.