APAR status
Closed as program error.
Error description
If the customer has an LTO volume mounted and the drive is power cycled or there is an interuption in power to the drive it is possible for TSM to over write the volume label for the volume mounted in the drive at the time of the power interuption. The issue would result in the following error: ANR8355E I/O error reading label for volume LTOXXX in drive XYZ. .. When there is an interuption in power to an LTO drive the drive does not dismount the volume as the 3590 and 3570 drives do. INSTEAD the device loads the tape and becomes ready. .. IF TSM is tracking the mounted volume as an idle volume and reopens the drive it is possible the GETREPORTDENSITY will receive the sense data associated to the bus reset and TSM will ignore it and assume the reopen finished without errors. TSM then relies on internal code to track the location of the tape but because of the power interuption the tape rewinds and the actual position of the volume and TSM's internal position are not the same and this may lead to an over write. You can check a TSM trace for the following: .. PVR I/O agent (37) processing REOPEN request. Reopening NTP volume LTO054. Getting capacity of cartridge loaded in drive DRV3581 (/dev/rmt6 Error performing GETREPORTDENSITY operation on drive DRV3581 (/dev/rmt6); errno = 5 Drive DRV3581 (/dev/rmt6): sense=70.00.06.00.00.00.00.1C.00.00.0 Found estimated capacity of 100000 for format 00000002 Found compression ratio of 2 for format 00000002. NtpOpGetMaxBlockSize:rc=0 Volume LTO054 blocksize=262144,....... .. PVR I/O agent (37) finished REOPEN request; rc=0. THE REQUEST to reopen the drive responds with an RC=0.
Local fix
For those customer's who do not have their drives connected to a UPS system and who have problems with their power source the MOUNTRetention to 0 to help reduce the exposure to this issue. Once a PTF is available for this issue apply the PTF and set the mountretention back to the desired value.
Problem summary
**************************************************************** * USERS AFFECTED: TSM 4.2 and 5.1 users with IBM LTO, 3590, or * * 3570 tape drives. * **************************************************************** * PROBLEM DESCRIPTION: Data can be overwritten if a tape * * drive is reset while TSM has control * * of the drive. * **************************************************************** * RECOMMENDATION: * **************************************************************** During certain commands issued after a tape has been IDLE TSM was ignoring unit attention errors being surfaced by the tape drive indicating that the tape is not longer positioned correctly. This problem only exists with IBM LTO, 3590, and 3570 tape drives on Windows, AIX, Linux, and Sun platforms.
Problem conclusion
All unit attention errors are now handled correctly. After the unit attention the tape will be re-positioned to the correct location. This will prevent data from being overwritten. This fix is available in the 4.2.3.3 and 5.1.6.1 patches and above.
Temporary fix
Comments
APAR Information
APAR number
IC35433
Reported component name
TSM SERVER 510
Reported component ID
5698ISMSV
Reported release
51S
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2003-01-16
Closed date
2003-01-29
Last modified date
2003-02-06
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
IC35562 IC35627
Fix information
Fixed component name
TSM SERVER 510
Fixed component ID
5698ISMSV
Applicable component levels
R51A PSY
UP
R51L PSY
UP
R51S PSY
UP
R51W PSY
UP
R51Z PSY
UP
R51H PSN
UP
R51P PSN
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"51S","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
06 February 2003