From: "Mr. Berkley Shands" <bshands@exegy.com>
To: linux-kernel@vger.kernel.org
Cc: linux-xfs@oss.sgi.com, linux-scsi@vger.kernel.org,
Dave Lloyd <dlloyd@exegy.com>
Subject: 2.6.20, XFS, mptsas and LSI-8888ELP write lockup
Date: Thu, 22 Mar 2007 11:00:54 -0500 [thread overview]
Message-ID: <4602A836.2010004@exegy.com> (raw)
I have a uniwide 3346, 20GB 8-core Opteron (2.2GHz)
With one LSI-8888ELP PCI-e SAS controller.
Each of the two external mini-sas 4-lane connectors goes to
an Xtore XJ-SAxx-316J-2 (16 drive 3U with dual SAS ports).
Running both Centos 4.4 or RedHat-5 Server with kernel 2.6.20.
The raids are all 4 drive raid0, 128KB stripes, using Seagate 7200.10
320GB drives (all firmware AAJ or later) Sata-II drives.
XFS filesystem, properly aligned, mkfs'ed etc.
If I write to all 4 VDs on one Xtore at a time, I get ~550MB/Sec
combined write rate. If I try writing to 7 of the 8 VDs at one time,
I get just under 800MB/Sec. Any 7 of 8 VDs.
But If I try to write to ALL 8 at once, the system crawls to a stop,
and I get Micro-Bytes per second.
xfs_datad/<N> process runs every few seconds, then pdflush runs
two or three at a time every few seconds. But iostat reports 0 writes.
every 10 seconds or so (iostat 5) reports a burst of write activity,
and then 10 seconds of nothing.
If I use the Adaptec 4805 (two of them), I get about
the same write rate, but it does not hang (AACRAID driver).
same type of file systems, same external enclosures.
I had a "echo 10 > /proc/sys/vm/dirty_ratio" fix in to correct slow
writes (vs 2.6.18), but altering this value changed nothing. It still
runs oh-so-slow.
What to look at next? 2.6.21-rc4 ?
berkley
--
//E. F. Berkley Shands, MSc//
**Exegy Inc.**
3668 S. Geyer Road, Suite 300
St. Louis, MO 63127
Direct: (314) 450-5348
Cell: (314) 303-2546
Office: (314) 450-5353
Fax: (314) 450-5354
The Usual Disclaimer follows...
This e-mail and any documents accompanying it may contain legally privileged and/or confidential information belonging to Exegy, Inc. Such information may be protected from disclosure by law. The information is intended for use by only the addressee. If you are not the intended recipient, you are hereby notified that any disclosure or use of the information is strictly prohibited. If you have received this e-mail in error, please immediately contact the sender by e-mail or phone regarding instructions for return or destruction and do not use or disclose the content to others.
[[HTML alternate version deleted]]
reply other threads:[~2007-03-22 16:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4602A836.2010004@exegy.com \
--to=bshands@exegy.com \
--cc=dlloyd@exegy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-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