On 01/14/2011 05:02 PM, Stan Hoeppner wrote:
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).
Just one P600.
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?
Nothing interesting in dmesg. iostat looks pretty dead on average.
During the dd write its doing about ~7tps according to iostat.
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?
Yes, it the throughput does increase with larger block sizes. I was
able to get ~13MB/s with 16k block size, still terrible however.
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?
The array is new and newly implemented.
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... :)
No, it has never worked properly. Also, I want to stress that I am only
having performance issues with one logical volume, the others seem fine.
------------------------------------------------------------------------
The information contained in this communication is intended
only for the use of the recipient(s) named above. It may
contain information that is privileged or confidential, and
may be protected by State and/or Federal Regulations. If
the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,
distribution, or copying of this communication, or any of
its contents, is strictly prohibited. If you have received
this communication in error, please return it to the sender
immediately and delete the original message and any copy
of it from your computer system. If you have any questions
concerning this message, please contact the sender.
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
