Fixes are available
APAR status
Closed as program error.
Error description
The Tivoli Storage Manager client journal-based backup daemon can fail to completely generate its journal database during an initial incremental backup. The following related errors can be found within the jbberror.log at the time of the failure: 10/01/2013 09:06:04 ANS0361I DIAG: psfsmon.cpp ( 873): psFsMonitorThread(tid 2): get pool RC=5022. Unable to access the specified file 10/01/2013 09:06:04 ANS0361I DIAG: psfsmon.cpp ( 570): psMonitorThread(): exiting RC=2. These errors cause the partially generated journal database to be destroyed, which prevents the journal from being enabled for the specified filesystem. Users will note that the following message is *not* printed to STDOUT during the initial incremental: ANS1760I Journal for 'X' enabled for node 'X' and server 'X' Successful incremental backup of 'X' Without this informational message, the journal is not enabled. This problem is more likely to occur when journal based backups are enabled against large filesystems on busy systems. Initial Impact: High Tivoli Storage Manager Versions Affected: All Linux Tivoli Storage Manager users of journal based backups. Additional Keywords: TSM MSGANS0361I DIAG TSMJBBD RC5022 PSMONITORTHREAD ANS1761I MEMORY UNABLE FILE SPECIFIED JOURNAL JOURNALING JBBD ANS1760I
Local fix
None. Continue using traditional incremental backups until the fix becomes available.
Problem summary
**************************************************************** * USERS AFFECTED: TSM 6.4 - TSM 7.1 Linux Journal Base * * Backup (JBB) users installed on Linux * * 2.6.32 kernel versions and higher. * **************************************************************** * PROBLEM DESCRIPTION: See ERROR DESCRIPTION * **************************************************************** * RECOMMENDATION: Apply fixing level when available. This * * problem is currently projected to be fixed * * in levels 6.3.2, 6.4.2 and 7.1.1. Note * * that this is subject to change at the * * discretion of IBM. * **************************************************************** *
Problem conclusion
Customers noticed that the Linux Journal Base Backup Daemon was receiving rc = 5022 from the Linux JBB driver. Deeper analysis revealed that memory allocation failures were printed in the /var/log/messages file. It was determined that the Linux JBB driver was attempting to allocate only continuous blocks of memory and some other device on the system was holding the needed space. A fix was put in place to allocate continuous memory blocks if they are available and to use virtual blocks otherwise.
Temporary fix
The GPL source code for JBB Linux is availble for the customer to compile due to the nature of how Linux kernel drivers are supported.
Comments
APAR Information
APAR number
IC97702
Reported component name
TSM CLIENT
Reported component ID
5698ISMCL
Reported release
63L
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-11-15
Closed date
2014-01-08
Last modified date
2014-01-08
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 CLIENT
Fixed component ID
5698ISMCL
Applicable component levels
R63L PSY
UP
R64L PSY
UP
R71L 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":"63L","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
08 January 2014