The topic title is intriguing, but we lack expected contextual
information about the problem (platform, OS, disk/tape technology,
etc.).
Magic number issues have historically occurred where TSM had written
data to media, the hardware did so without issue, and later TSM tries
to read it back, which the hardware does without detection of errors;
but the data is nonetheless corrupt. The cause can be faulty
hardware, erroneous firmware, bad SCSI cables, network infrastructure
problems, and the like, which can all result in bad data ending up on
the media.
It's unlikely that your OS error log has any entries to help in this,
but check. You might also check back in your Activity Log for when
the data was first written by TSM, for any indications then.
Unless you can find and correct any hardware problems, your only
recourse may be reattempts of the migration, and possibly doing Move
Data to move off as much good data as possible. Whereas this sounds
like you are moving from disk to tape, and such errors have been on
reading, you should consider not using this disk system until its
problems can be uncovered and corrected. (Do backups directly to tape
until then.) Check your site records of system changes to see if any
conditions may have changed to cause this.
Richard Sims
On Jul 20, 2005, at 3:10 PM, Lepre, James wrote:
Hello Everyone
I am getting the following errors in the activity log. This occurs
during migration. Here is the output of both migration and activity
log. Any help would surely be appreciated..
Thank you
James
40 Migration Disk Storage Pool NECATSMDR_STORAGEPOOL, Moved
Files: 76383, Moved Bytes: 139,613,954,048, Unreadable Files: 3575774,
Unreadable Bytes: 5,863,056,785,408. Current Physical File (bytes):
6,756,592
Current output volume: 010244.
07/20/05 14:16:33 ANR1331E Invalid frame detected. Expected magic
53454652 sequence number 00000001 server id 00000000 segment id
0000365965637. (SESSION: 6110, PROCESS: 40)
7/20/05 14:16:33 ANR1330E The server has detected possible
corruption in an object being restored or moved. The actual values for
the
incorrect frame are: magic 3E0AD753 hdr version 40583 hdr
length 25025 sequence number 2064952911 data length 129
464C1 server id 1387798037 segment id 8720201161928875533
crc 105E63C1. (SESSION: 6110, PROCESS: 40)
|
