I am getting an error from my tsm 5.1.8 server on AIX that I have not been able to track and correct. Actually this condition creates deadlock and the system is unavailable for any operations. Here a section of my activity log:
02/18/04 03:14:07 ANR0984I Process 32 for MIGRATION started in
the
BACKGROUND at
03:14:07.
02/18/04 03:14:07 ANR1000I Migration process 32 started for storage
pool BACKUPPOOL.
02/18/04 03:14:08 ANR8468I LTO volume CART01 dismounted from drive
3581DRV
(/dev/rmt1) in library
3581LIBR.
02/18/04 03:14:55 ANR8337I LTO volume CART01 mounted in drive
3581DRV (/dev/rmt1).
02/18/04 03:15:32 ANR8341I End-of-volume reached for LTO volume
CART01.
02/18/04 03:15:35 ANR1025W Migration process 32 terminated for
storage pool
BACKUPPOOL - insufficient space in subordinate
storage pool.
02/18/04 03:15:35 ANR0985I Process 32 for MIGRATION running in
the
BACKGROUND completed with completion state
FAILURE at
03:15:35.Here is the output of my "query vol cart01 format=detailed" command for CART01:
Volume Name: CART01
Storage Pool Name: 3581STGPOOL
Device Class Name: 3581DEVCLASS
Estimated Capacity (MB): 190,734.0
Pct Util: 29.4
Volume Status: Filling
Access: Read/Write
Pct. Reclaimable Space: 39.9
Scratch Volume?: No
In Error State?: No
Number of Writable Sides: 1
Number of Times Mounted: 2,490
Write Pass Number: 2
Approx. Date Last Written: 02/17/04 10:43:48
Approx. Date Last Read: 02/17/04 15:49:12
Date Became Pending:
Number of Write Errors: 0
Number of Read Errors: 0
Volume Location:
Last Update by (administrator): ADMIN
Last Update Date/Time: 02/17/04 10:39:23Can anyone understand why a 29.4 percent utilization volume will create the errors above? Any way to correct this sistuation. The only way I found was to remove the volume and relable it. Now, I am not a TSM expert so I may be missing the obvious...... so shoot if you must!
Thanx Andreas
--
Andreas Kasenides e-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
