2.3.8. 'ANS4023E Error processing ...: file input/output error' or 'ANS4046E There is an error processing ... the object is corrupted and unreadable' or 'ANS4047E There is a read error on .... The file is skipped.'

If TSM is having trouble reading certain files, then it could be because they are corrupted. If this is the case then you will see error messages in your dsmerror.log about certain files being unreadable by TSM. For example, they may take the form:

ANS4023E Error processing '/var/log/test.log': file input/output error.
ANS4046E There is an error processing '/var/log/test.log': the object is corrupted and unreadable.
ANS4047E There is a read error on '/var/log/test.log'. The file is skipped.

If the fault is only software-related, then the problem can be fixed by checking the disk. Basic steps are as follows, though you may want to do further research before implementing them.
  • In Windows, in My Computer, right-click on the offending drive (e.g. C:), and select [Properties] > [Tools]. Then, under 'Error-checking', click on Check Now and tick the box marked 'Automatically fix file system errors', then Start. Click Yes to the question about running a disk check the next time the computer is restarted. Any file system errors that are easily fixable will then be fixed on the next reboot.
  • On a Mac, in Finder, go [Applications] > [Utilities] > [Disk Utility]; then, in the left-hand window, click on the relevant drive and, in the [First Aid] tab click Verify Disk or, if appropriate, Repair Disk.
  • In Linux or Solaris, use the command fsck to check your disk - please refer to your system documentation for the appropriate procedure.

In the worst case scenario, if you have file errors despite trying to fix them, or if you are concerned that your hard disk may have a fault, please see your local IT for advice.

Up: Contents Previous: 2.3.7. Backup simply stops - no ANS error or warning message Next: 2.3.9. 'ANS1310E Object too large for server limits'