Fixes are available
APAR status
Closed as program error.
Error description
The Tivoli Storage Manager can potentially overwrite a file volume when the results from the operating system (OS) are invalid. This has only been reported on Network File Systems (NFS). When the server is going through the process to determine a new volume name, the directory is queried to see if the name already exists. If the OS relays the file does not exist then the server will create a 0 byte file using the new name. In this particular case, the OS returned that the file did not exist when in fact the file existed. Refer to the Diagnostic section below for additional details. Tivoli Storage Manager Versions Affected: 5.5, 6.1, 6.2, 6.3 and 7.1 Customer/L2 Diagnostics (If Applicable): This is only seen when you can issue an OS command to list the contents of a directory or the specifics of a file and the OS returns nothing or reports that the file does not exist. For example: root:prod# ls -l /tsm/00000090.bfs ls: 0653-341 The file /tsm/00000090.bfs does not exist. Then you issue the command again and it shows the following: root:prod# ls -l /tsm/00000090.bfs -rw------- 1 root system 1073741 /tsm/00000090.bfs One the server, the only way you might be able to see this occurring is the following message: ANR8449E Scratch volume /tsm/00000001.BFS rejected - volume name is already in use. This message indicates the server attempted to create the new volume but then realized there was already a reference to the file in the DB. At that time, the server will attempt to get a new volume name. The above message does not necessarily mean that your data has been overwritten because first the OS needs to be retuning inconsistent results. Initial Impact: Medium Additional Keywords: NFS LS CORRUPTION OVERWRITTEN
Local fix
1) Determine why the OS is returning inconsistent results. 2) Restore the data from a copypool, otherwise, the data is lost.
Problem summary
**************************************************************** * USERS AFFECTED: All Tivoli Storage Manager server users. * **************************************************************** * PROBLEM DESCRIPTION: See ERROR DESCRIPTION. * **************************************************************** * RECOMMENDATION: Apply fixing level when available. This * * problem is currently projected to be fixed * * in levels 6.3.5 and 7.1.1. Note that this is * * * * subject to change at the discretion of IBM. * **************************************************************** *
Problem conclusion
This problem was fixed. Affected platforms: AIX, HP-UX, Solaris, Linux, and Windows.
Temporary fix
Comments
APAR Information
APAR number
IC98531
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
55A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-12-31
Closed date
2014-01-27
Last modified date
2014-01-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TSM SERVER
Fixed component ID
5698ISMSV
Applicable component levels
R63A PSY
UP
R63H PSY
UP
R63L PSY
UP
R63S PSY
UP
R63W PSY
UP
R71A PSY
UP
R71H PSY
UP
R71L PSY
UP
R71S PSY
UP
R71W PSY
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":"55A","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
27 January 2014