You might also check your diskpool volume count. If its low, assuming
your doing raw logical volumes, you might want to try decreasing the
size of your volumes and thereby increasing the count of your volumes .
A small number of large volumes does not allow several clients or
processes to stream data to the storage pools efficiently.  


Joy Hanna
Enterprise Storage Group
I.T. Computer Operations
(503)745-7748
Joyhanna AT freightliner DOT com

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Craig Ross
Sent: Friday, July 27, 2007 2:49 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM performance very poor, Recovery log is being
pinned

10 days ago I Recently added 15TB of SATA storage and a new Fabric with
4 new LTO drives to our 3584 library, The DB is approx 90GB TSM

Few days ago I noticed processing had ground to halt, after digging
around I have found as soon as server gets busy maybe 4 processes 8 or
so sessions the recovery log begins "sh logpinned" to pin and the
Database gets locks.
Shown by running "sh locks"
And as result the server suffers!
Now today I have stopped using the new Tech LTO 3 and SATA and things
are coping better but still worse than previous as soon as load is
increased Log pins and processing slows drastically.

Are there any steps I can take which will help my scenario.
Would a DB UNLOAD RELOAD help that much?

Reference: Recovery log has heaps of room DB has heaps of room 90Gb DB
with 100GB of room.

Any advice is much appreciated.