From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: XFS hangs and freezes with LSI 9265-8i controller on high i/o
Date: Wed, 13 Jun 2012 14:13:23 +0200 [thread overview]
Message-ID: <6637532.ZKYiNbq2uo@saturn> (raw)
In-Reply-To: <20120613115934.GX32601@systemlinux.org>
[-- Attachment #1.1: Type: text/plain, Size: 1207 bytes --]
Am Mittwoch, 13. Juni 2012, 13:59:34 schrieb Andre Noll:
> 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
I wanted to comment on the original posting, but it fits here too. Aside
from this performance perspective, in order to have a system that
survives crashes and powerouts, better use:
Disk (Write) Cache: disabled (is that Disk Cache Policy for writes, or
read+writes?)
Write Cache DISABLED if Bad BBU
While turning off disk write caches costs some performance always,
disabling the controller write cache if the bbu is dead makes the server
only slower during bbu outages, but at least it will survive a crash
then.
It depends on your needs, but I don't know an admin with a +40TB storage
that says "doesn't matter if it breaks, I'll restore from backup", as
even with disk2disk backup that takes some time.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- 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
next prev parent reply other threads:[~2012-06-13 12:13 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
2012-06-13 12:13 ` Michael Monnerie [this message]
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=6637532.ZKYiNbq2uo@saturn \
--to=michael.monnerie@is.it-management.at \
--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