Question & Answer
Question
When TSM client is not able to read the file contents during backup, it reports "Read Failure" like in the following example: Directory--> 512 /testdir [Sent] Normal File--> 4,823,567 /testdir/file1 Read Failure Retry # 1 Normal File--> 4,823,567 /testdir/file1 Read Failure Retry # 2 Normal File--> 4,823,567 /testdir/file1 Read Failure Retry # 3 Normal File--> 4,823,567 /testdir/file1 Read Failure Retry # 4 Normal File--> 4,823,567 /testdir/file1 Read Failure ANS1228E Sending of object '/testdir/file1' failed Read Failure
Cause
TSM is using standard operating system calls to read file contents and reports a failure if a call returns an error. In most cases this means the file is not readable. This could happen because of a hardware problem or file system integrity problem.
Answer
To see if the file is readable, try copying it to another location by standard operating system tools. For example, you can use 'cp' or 'dd' command on Unix, and 'copy' command or Windows Explorer on Microsoft Windows. If the file is not readable, the copying operation should fail too.
To repair a corrupted file system or disk hardware problems, please use the tools available for your operating system. Most common tools are 'fsck' on Unix and 'chkdsk' on Windows.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21201865