From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: extremely slow write performance plaintext
Date: Fri, 14 Jan 2011 13:51:33 -0600 [thread overview]
Message-ID: <4D30A945.4060000@hardwarefreak.com> (raw)
In-Reply-To: <18993_1294964274_4D2F9632_18993_1387_1_F79CF9ADB27B2646B59221B7355263830CC143B1@NYL-EXCH1.HVHCVision.com>
Cory Coager put forth on 1/13/2011 6:17 PM:
> --- Physical volume ---
> PV Name /dev/cciss/c1d1p1
> VG Name vg0
> PV Size 2.94 TB / not usable 1.51 MB
> Allocatable yes
> PE Size (KByte) 4096
> Total PE 769902
> Free PE 562351
> Allocated PE 207551
> PV UUID IAZAbk-eMNZ-puMJ-DqW1-zsC7-C0ux-66vYTN
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...
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.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-01-14 19:49 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 [this message]
2011-01-14 20:48 ` Cory Coager
2011-01-14 22:02 ` Stan Hoeppner
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=4D30A945.4060000@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