public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Matthew Whittaker-Williams <matthew@xsnews.nl>, xfs@oss.sgi.com
Subject: Re: XFS hangs and freezes with LSI 9265-8i controller on high i/o
Date: Tue, 12 Jun 2012 22:56:14 -0500	[thread overview]
Message-ID: <4FD80F5E.3080007@hardwarefreak.com> (raw)
In-Reply-To: <20120613011950.GN22848@dastard>

On 6/12/2012 8:19 PM, Dave Chinner wrote:
> On Tue, Jun 12, 2012 at 05:56:23PM +0200, Matthew Whittaker-Williams wrote:

>> RAID Level          : Primary-6, Secondary-0, RAID Level Qualifier-3
>> Size                : 40.014 TB
>> State               : Optimal
>> Strip Size          : 64 KB
>> Number Of Drives    : 24
> .....
>> Virtual Drive: 1 (Target Id: 1)
>> Name                :
>> RAID Level          : Primary-6, Secondary-0, RAID Level Qualifier-3
>> Size                : 40.014 TB
>> State               : Optimal
>> Strip Size          : 1.0 MB
>> Number Of Drives    : 24

> The reason, I'd suggest, is that you've chosen the wrong RAID volume
> type for your workload. Small random file read and write workloads
> like news and mail spoolers are IOPS intensive workloads and do
> not play well with RAID5/6. RAID5/6 really only work well for large
> files with sequential access patterns - you need to use RAID1/10 for
> IOPS intensive workloads because they don't suffer from the RMW
> cycle problem that RAID5/6 has for small writes. The iostat output
> will help clarify whether this is really the problem or not...

If it is the problem, you'll want to consider something like the
following, assuming your working files are somewhat evenly spread over
24 or more directories and/or subdirectories.

1.  For each 24 drive JBOD, create 3x 8 drive RAID10s, strip 64KB.  That
yields a relatively small stripe of 256KB over 4 spindles.  Should be a
good fit for small file random IOPS.

2.  Make an md linear array of the 3 hardware RAID10 arrays, such as:

~$ mdadm -C /dev/md0 -n3 -l linear /dev/sd[abc]

3.  Create your stripe aligned XFS over the md linear array:

~$ mkfs.xfs -d su=64K,sw=4 agcount=24

This will yield excellent small file IOPS, ~1800 peak at the spindles,
while still giving a decent ~400MB/s kick if you have some streaming
workloads from time to time.  Absolute XFS small file high IOPS
performance is attained with a linear array of RAID1 pairs, but with 12
physical device names this tends to get unwieldy in mdadm.  And as I
mentioned this hybrid architecture still allows decent streaming
performance if you need it.

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-06-13  3:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 21:37 XFS hangs and freezes with LSI 9265-8i controller on high i/o Matthew Whittaker-Williams
2012-06-12  1:18 ` Dave Chinner
2012-06-12 15:56   ` Matthew Whittaker-Williams
2012-06-12 17:40     ` Matthew Whittaker-Williams
2012-06-13  0:12     ` Stan Hoeppner
2012-06-13  1:19     ` Dave Chinner
2012-06-13  3:56       ` Stan Hoeppner [this message]
2012-06-13  8:54       ` Matthew Whittaker-Williams
2012-06-13 11:59         ` Andre Noll
2012-06-13 12:13           ` Michael Monnerie
2012-06-13 16:12             ` Stan Hoeppner
2012-06-14  7:31               ` Michael Monnerie
2012-06-14  0:04         ` Dave Chinner
2012-06-14 14:31           ` Matthew Whittaker-Williams
2012-06-15  0:16             ` Dave Chinner
2012-06-15  9:52               ` Michael Monnerie
2012-06-15 12:29                 ` Dave Chinner
2012-06-15 11:25               ` Bernd Schubert
2012-06-15 12:30                 ` Dave Chinner
2012-06-15 14:22                   ` Bernd Schubert

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=4FD80F5E.3080007@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=david@fromorbit.com \
    --cc=matthew@xsnews.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox