Hi TSM'ers During an incremental backup, we see the folowing errors everytime it attempts to backup a dir called
/oradata20/FRSCID3 (This errorlog was generated manually outside of a scheduled backup) 10/01/01 12:54:30 TransErrno: Unexpected error from lstat, errno = 72 10/01/01 12:54:30 TransErrno: Unexpected error from lstat, errno = 72 10/01/01 12:54:30 PrivIncrFileSpace: Received rc=131 from fioGetDirEntries: /oradata20 /FRSCID3 10/01/01 12:54:33 ANS1074I *** User Abort *** 10/01/01 12:54:43 TransErrno: Unexpected error from lstat, errno = 72 10/01/01 12:54:43 TransErrno: Unexpected error from lstat, errno = 72 10/01/01 12:54:43 PrivIncrFileSpace: Received rc=131 from fioGetDirEntries: /oradata20 /FRSCID3 10/01/01 12:54:46 ANS1074I *** User Abort *** The dsmc session shows; root@oradev2[oradata20]dsmc i ./ Tivoli Storage Manager Command Line Backup Client Interface - Version 4, Release 1, Level 2.0 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. Node Name: ORADEV2 Session established with server MDADUX0001: Solaris 2.6/7 Server Version 3, Release 7, Level 4.9 Server date/time: 10/01/01 12:55:26 Last access: 10/01/01 12:51:25 Incremental backup of volume './' Successful incremental backup of '/oradata20/*' Total number of objects inspected: 6 Total number of objects backed up: 0 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred: 0 Bytes Data transfer time: 0.00 sec Network data transfer rate: 0.00 KB/sec Aggregate data transfer rate: 0.00 KB/sec Objects compressed by: 0% Elapsed processing time: 00:00:03 ANS1074I *** User Abort *** There are many files under FRSCID3, -subdir is Y, yet the backup session never see's the files under FRSCID3. Does anyone know what errno 72 is from lstat, or 131 from fioGetDirEntries ? oradata20 is a mountpoint for an HPUX LVM logical volume. The TSM client is 4.1.2.0, HPUX version B.11.00 from uname -a The physical disk/s the logical volume resides on are dual pathed Fibre Attatched EMC Symmetrix devices. The O/S is using pvlinks to give crude load balancing/failover, we are also using VolumeLogix and Connectrix manager to controll what devices this host can see on the symmetrix.
