public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Noll <maan@systemlinux.org>
To: Matthew Whittaker-Williams <matthew@xsnews.nl>
Cc: xfs@oss.sgi.com
Subject: Re: XFS hangs and freezes with LSI 9265-8i controller on high i/o
Date: Wed, 13 Jun 2012 13:59:34 +0200	[thread overview]
Message-ID: <20120613115934.GX32601@systemlinux.org> (raw)
In-Reply-To: <4FD8552C.4090208@xsnews.nl>


[-- Attachment #1.1: Type: text/plain, Size: 986 bytes --]

On Wed, Jun 13, 10:54, Matthew Whittaker-Williams wrote:
> Current Cache Policy: WriteBack, ReadAheadNone, Direct, Write Cache OK if Bad BBU
> Disk Cache Policy   : Disk's Default

Check if these two policy settings are what you really want. AFAICT
they can make a huge difference, depending on the workload.

Here's what gives best performance. Of course these are also the most
risky settings, so use with care:

	Current Cache Policy: WriteBack, ReadAdaptive, Cached, Write Cache OK if Bad BBU
	Disk Cache Policy: Enabled

To select these settings for all lds on adapter 0, use

	CLI=MegaCli; lsi_adapter_number=0
        $CLI -ldsetprop CachedBadBBU -LALL -a$lsi_adapter_number &&
        $CLI -ldsetprop -Cached -LAll -a$lsi_adapter_number &&
        $CLI -ldsetprop -EnDskCache -LAll -a$lsi_adapter_number &&
        $CLI -ldsetprop WB -LALL -a$lsi_adapter_number

Best
Andre
-- 
The only person who always got his work done by Friday was Robinson Crusoe

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

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

  reply	other threads:[~2012-06-13 11:58 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
2012-06-13  8:54       ` Matthew Whittaker-Williams
2012-06-13 11:59         ` Andre Noll [this message]
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=20120613115934.GX32601@systemlinux.org \
    --to=maan@systemlinux.org \
    --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