IC99853: AUTOMATIC CLIENT DEPLOYMENT FAILS WITH 'ANS4253E THERE WAS NOT ENOUGH DISK SPACE ON THE CLIENT COMPUTER'.

IBM Tivoli Storage Manager (TSM) client 7.1.0.x interim fix downloads
IBM Tivoli Storage Manager (TSM) Client 7.1.1 Downloads and READMEs
IBM Tivoli Storage Manager (TSM) client 6.3.2.x interim fix downloads - EOL

APAR status

• Closed as program error.

Error description

• Tivoli Storage Manager automatic client deployment on Unix and
  Linux platforms, can fail with
  'ANS4253E There was not enough disk space on the  client
  computer'
  if a target filesystem wraps onto 2 lines in the command output
  of 'df -k'.
  
  In updatemgr.log it is seen:
  
  02/18/14   16:20:15 ANS4200I  x86_64, UPDATE_CLIENTS_641,
  IBM_CLIENT_DEPLOY: The Deployment Manager process was started
  successfully.
   Deployment Manager Version Information: Deployment Manager
  Version 1,
  Release 2, Level 0.0 110307A
  .
  02/18/14   16:20:15 ANS4253E There was not enough disk space on
  the
  client computer. Required space: 838860800 bytes; available
  space
  : 49152 bytes.
  02/18/14   16:20:15 ANS4298E  x86_64, UPDATE_CLIENTS_641,
  IBM_CLIENT_DEPLOY: The client deployment was cancelled. The
  previous
  causing the cancellation is: 4253.
  
  
  
  L2/Customer diagnostics:
  
  
  .
  In client 'service' trace:
  ...
  02/18/14   16:20:15.792 : dsmtrace.cpp        ( 146): Deployment
  Manager
  Version 1, Release 2, Level 0.0 110307A
  ...
  02/18/14   16:20:15.793 : dsmtrace.cpp        ( 146): DeployMgr
  psupdatemgr.cpp(752): Required space: 838860800 bytes; available
  space:
  49152 bytes.
  02/18/14   16:20:15.793 : dsmlog.cpp          ( 598):
  dsmHandle=1
  logFlags  = 0x00000002 msgNum>14253< numInserts>2<
  02/18/14   16:20:15.811 : dsmlog.cpp          ( 662):
  tsmLogMessage
  EXIT: rc = >0<.
  02/18/14   16:20:15.811 : dsmlog.cpp          ( 598):
  dsmHandle=1
  logFlags  = 0x00000002 msgNum>14298< numInserts>4<
  02/18/14   16:20:15.812 : dsmlog.cpp          ( 662):
  tsmLogMessage
  EXIT: rc = >0<.
  02/18/14   16:20:15.812 : dsmtrace.cpp        ( 146): DeployMgr
  psupdatemgr.cpp(773): Terminating update manager. Insufficient
  disk space.
  Required space: 838860800 bytes; available space: 49152 bytes.
  ...
  .
  The df -k from the filesystem shows wrapped around lines like
  ...
  /dev/mapper/rootvg-opt
                        10321208   4543340   5253580  47% /opt
  ...
  So here the psdeployclient.sh script would read the 47 instead
  of the 5253580, thus failing the upgrade as
  calculated available space : 49152 bytes is less than  Required
  space: 838860800 bytes;
  
  
  Tivoli Storage Manager Versions Affected:
  Tivoli Storage Manager Clients 6.2.x, 6.3.x, 6.4.x and 7.1.x on
  AIX, Solaris, HPUX and Linux platforms
  
  
  Initial Impact:
  Medium
  
  Additional Keywords:
  zz62 zz63 zz64 zz71 client deployment df space
  

Local fix

• Upgrade client manually
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All linux users where there is a mount       *
  *                 point with more than 20 characters and       *
  *                 attempt to use autodeployment.               *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION                   *
  ****************************************************************
  * RECOMMENDATION: Apply the fixing level when available.  This *
  *                                                              *
  *                 problem is currently projected to be fixed   *
  *                 in levels 7.1.1 and 6.4.2                    *
  ****************************************************************
  The script used to determine free space did not use the
  correct option that allowed for mount points longer than
  20 characters.
  

Problem conclusion

• The update manager component of auto deployment was updated
  to correctly work with mount points of more than 20
  characters.
  

Temporary fix

• A fix for this problem is currently targeted for the 7.1.0.3
  Until the interim fix is actually available this information
  is subject to change at the discretion of IBM.
  

Comments

APAR Information

• 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

• R64L PSY

     UP

• R71L PSY

     UP