public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: extremely slow write performance plaintext
Date: Fri, 14 Jan 2011 16:02:27 -0600	[thread overview]
Message-ID: <4D30C7F3.3040105@hardwarefreak.com> (raw)
In-Reply-To: <27616_1295038110_4D30B69E_27616_233_1_4D30B69E.4020506@davisvision.com>

Cory Coager put forth on 1/14/2011 2:48 PM:
> On 01/14/2011 02:51 PM, Stan Hoeppner wrote:
>> Make sure the write cache on the P600 (what size is it BTW?) is enabled and that
>> the BBU is in working order.  Also make sure the P600 is disabling the write
>> caches on the drives themselves.  Then...
>>
> Write cache is enabled on the controller, the size is 512MB, BBU is in good
> conditioned (checked with the HP utility).  How do I check the write cache on
> the drives?

The controller should do this automatically.  You'll have to check the docs to
verify.  This is to safeguard data.  The BBWC protects unwritten data in the
controller cache only, not the drives' caches.  It won't negatively affect
performance if the drives' caches are enabled.  On the contrary, it would
probably increase performance a bit.  It's simply less safe having them enabled
in the event of a crash.

After rereading your original post I don't think there's any issue here anyway.
 You stated you have 24 drives in 2 arrays (although you didn't state if all the
disks are on one P600 or two).

>> Mount with 'nobarrier' so XFS isn't interfering with the hardware cache
>> performance of the P600.  With barriers enabled (the default) XFS will
>> periodically flush the cache on the RAID card causing write performance problems.
>>
> Already using nobarrier.

This was the important part I was looking for.  It's apparently not a cache
issue then, unless the utility is lying or querying the wrong controller or
something.

Nothing relevant in dmesg or any other logs?  No errors of any kind?  Does
iostat reveal anything even slightly odd?

I also just noticed you're testing writes with a 1k block size.  That seems
awefully small.  Does the write throughput increase any when you test with a
4k/8k/16k block size?

BTW, this is an old machine.  PCI-X is dead.  Did this slow write trouble just
start recently?  What has changed since it previously worked fine?

You're making it very difficult to assist you by not providing basic
troubleshooting information.  I.e.

What has changed since the system functioned properly?
When did it change?
Did it ever work properly?
Etc.

God I hate pulling teeth... :)

-- 
Stan

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

  reply	other threads:[~2011-01-14 22:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 21:22 extremely slow write performance plaintext Cory Coager
2011-01-13 22:35 ` Emmanuel Florac
2011-01-14  0:17   ` Cory Coager
2011-01-14 19:51     ` Stan Hoeppner
2011-01-14 20:48       ` Cory Coager
2011-01-14 22:02         ` Stan Hoeppner [this message]
2011-01-18 14:16           ` Cory Coager
2011-01-19  9:59             ` Stan Hoeppner
2011-01-25 14:22               ` Cory Coager
2011-01-25  6:21             ` Michael Monnerie
2011-01-25  9:48               ` Mathieu AVILA
2011-01-25 14:25                 ` Cory Coager
2011-01-28  6:22                   ` Michael Monnerie
2011-01-28 13:08                     ` Cory Coager
2011-01-25 14:27               ` Cory Coager

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=4D30C7F3.3040105@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --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