RE: ASP arm %busy imbalance.

Sue and Rob,

All have parity data.
One raid set with 8 disk.

1  4326    30769  53,0
2  4326    30769  53,0
3  4326    30769  53,0
4  4326    30769  53,0
5  4326    30769  53,0
6  4326    30769  53,0
7  4326    30769  53,0
8  4326    30769  53,0

I do not now what kind of job where runing at the moment.

No i was not cleaning up old journal receivers when this happened.

I will try the TRCASPBAL and then a straspbal *usage



Regards Jan Rockstedt
Avinova AB
nic-hdl: JR1543-RIPE

See you at Common Congress Stockholm 11-13 juni 2006!
Common Europe and Data3 in partnership with IBM     www.comeur.org



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sue Baker
Sent: Thursday, April 06, 2006 5:36 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: ASP arm %busy imbalance.

Jan Rockstedt wrote on Thu, 06 Apr 2006 09:02:01 GMT:

> Any sugestion better performance on the ASP arm?
> 

Do all of your arms have parity data on them or are some "full size" and
just part of a parity set?  

Are all of your arms the same percent full?

Were you running any sort of a job that would be accessing data such
that the job could create a "hot spot" effect?  

Were you possibly cleaning up old journal receivers when this happened?
(One way to hot spot a drive or set of drives is to have journaling
picking those drives for all the receiver
entries.)

--
Sue
System i5 Advanced Technical Sales Support Rochester, MN

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.