Anr8300e I O Error On Library Ts3500
Contents |
LARGE NUMBER OF STORAGE SLOTS AIX Fixes are available IBM Tivoli Storage Manager V6.1 Fix Pack 2 http://www.ibm.com/support/docview.wss?uid=swg1IC61218 (6.1.2) Server Downloads IBM Tivoli Storage Manager V6.1 Fix Pack 3 https://www.mail-archive.com/search?l=adsm-l@vm.marist.edu&q=subject:%22Inconsisent+behavior+of+mount+errors+on+scratch+tapes.%22&o=newest&f=1 (6.1.3) Server Downloads Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description When checking in volumes using checkin libvol or label libv with the checkin parameter, and the search=yes parameter is also used, ANR8300E can o error occur on libraries which have a large number of storage slots. The tape library must be controlled by the TSM device driver for this apar to apply. - The problem is that the TSM device driver will time out the checkin command if it runs longer than 30 minutes. These messages will occur in the activity o error on log if this problem exists: - 05/18/2009 14:48:05 ANR2017I Administrator ADMIN issued command CHECKIN libv LIBRARY search=yes status=private checkl=barcode (SESSION: XXXX) 05/18/2009 15:18:06 ANR8300E I/O error on library LIBRARY (OP=00006C04, CC=205, KEY=FF, ASC=FF, ASCQ=FF, SENSE=**NONE**, Description=SCSI adapter failure). Refer to Appendix C in the 'Messages' manual for recommended action. (SESSION: XXXX, PROCESS: XX) - Timestamps for the error should be 30 minutes apart. - Notes: 1. ANR8300E can occur for other reasons. The ASC, ASCQ and lack of sense data need to exist, as well as the 30 minute time period for the problem to match this apar. - 2. A similar problem can exist for tape libraries which are controlled by the IBMtape device driver. The fix for the problem in this apar does not affect similar problems on IBMtape controlled libraries. IBMtape support should be engaged if this problem is encountered with an IBMtape controlled library. See knowledge document 1368357. Tivoli Storage Manager Versions Affected: 5.4, 5.5, and 6.1 servers on all platf
Case 1. Full backup of a TDP for exchange node. TSM 5.4.4.0 for Windows Server, TSM client 5.3.6, Storage agent 5.3.6, TDP for Exchange 5.3.3.1 TS3100 library with LTO3 drives. LAN Free TDP backup is part way through and goes to mount the next tape. Tape mount fails... 02/26/2009 04:16:48 ANR8944E Hardware or media error on drive DRIVE1 (\\.\Tape2) with volume DIA142L3(OP=TESTREADY, Error Number= 23, CC=0, KEY=03, ASC=53, ASCQ=00, SENSE=70.00.03.00.00.00.00.58.00.00.00.00.53.00.36.00.2E- .07.00.02.00.02.20.20.20.20.20.20.20.00.00.00.24.98.01.7- 4.00.00.00.00.00.00.00.00.00.00.00.00.00.00.12.02.00.00.- 00.00.00.00.00.60.00.00.00.00.70.00.03.00.00.00.00.58.00- .00.00.00.53.00.36.00.2 E.07.00.02.00.02.20.20.20.20.20.2- 0.00.00.00, Description=An undetermined error has occurred). Refer to Appendix C in the 'Messages' manual for recommended action. (SESSION: 995) 02/26/2009 04:16:48 ANR8304E Time out error on drive DRIVE1 (\\.\Tape2) in library ATL. (SESSION: 995) 02/26/2009 04:16:48 ANR8945W Scratch volume mount failed DIA142L3. (SESSION: 995) 02/26/2009 04:17:17 ANR8381E LTO volume DIA142L3 could not be mounted in drive DRIVE1 (\\.\Tape2). (SESSION: 995) 02/26/2009 04:17:17 ANR9790W Request to mount volume *SCRATCH* for library This is the only scratch tape in the library and is physically damaged. The TDP aborts the transaction, and retries the backup which writes to the end part of the first tape until it is full, at which point it tries to mount the scratch again, gets the same error, and the cycle repeats. Case 2. Library Manager/Library client set up, Multiple P595 AIX LPARS. One TSM Server is set up as Library manager and Config Manager. 4 library client servers, all at TSM Server 5.5.1.0 . Big TS3500 library, 30 drives and 2500 LTO4 tapes. This site is ramping up and has about 2000 scratch tapes. For reasons that we haven't quite understood yet, tapes are being left in drives and not properly dismounted. Thats not the interesting part. A library client tries to mount a scratch on a drive that is unable to do so, this produces an immediate IO error. In this case the scratch that had the IO error is marked private. TSM assumes the problem is the *tape* and attempts to mount the next available scratch in the same drive. Again this gets the IO error and is marked private. In a minute or two the server has run through all 2000 scratches and we have none left 02/24/2009 03:01:22 ANR8300E I/O error on library LTOCV1 (OP=6C03, CC=207, KEY=05, ASC=21, ASCQ=01, SENSE=70.00.05.00.00.00.00.0 A.0- 0.00.00.00.21.01.00.C0.00.06., Description=Device is not in a state capable of performing request). Refer to Appendix C in the 'Messa