You're not giving us enough information to understand what the actual problem is there. Disk storage pool space and Recovery Log space are very different things and very much should be in very different places, having different service and recovery needs, including mirroring for the TSM database and recovery log.
With AIX, you should ideally be using Raw Logical Volumes, as described in the Admin Guide and other TSM documentation, such as the Performance Tuning Guide. This will eliminate all the file system issues and greatly facilitate disaster recovery. Always thoroughly review vendor configuration recommendations before proceeding with an implementation. And always implement monitoring, to avoid needless disruptions like this. Again, I won't add further recommendations, absent the solid information needed to provide proper guidance. Richard Sims On Sep 26, 2006, at 6:29 AM, Adrian Compton wrote:
Hi Yesterday my TSM server (p500 LPAR AIX 5.3) had the TSM Logs run out of space. In hind sight, the Server was bounced and I now have fsck running forever almost as if in a loop. At present it would take days as the filesystem concerned is 1.150TB. Apparently we need to patch the OS as the FSCK gets into a loop, and has to complete the checks of the superblocksbefore it can be mounted. This filesystem contains my DISKPOOLS. My questions are/ 1. Will any clients that normally go to DISPOOL now automatically go to overflow until the filesystem comes backup. 2. what is the recommended max filesystem size to prevent this long FSCK. 3. Is there any other way to resolve this long wait for the check to complete. Regards Adrian Compton
