ADSM-L

Re: ANR13300E & ANR1331E

2005-11-01 16:18:41
Subject: Re: ANR13300E & ANR1331E
From: "Bos, Karel" <Karel.Bos AT ATOSORIGIN DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 1 Nov 2005 22:17:55 +0100
Hi,

A while ago we had these errors also. In our case these errors where
seen during migration (diskp -> tapepool) and/or backup stg diskpool ->
copypool.

In only one case we could pin point it to hardware failures (one disk at
breaking point in the diskpool). In all other cases it seems to be
network related (corrupted data frames).

After a couple of back-up runs, the errors went away and I haven't seen
them back yet. (server park is relocated and replaced).

Regards,

Karel
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Timothy Hughes
Sent: dinsdag 1 november 2005 19:36
To: ADSM-L AT VM.MARIST DOT EDU
Subject: ANR13300E & ANR1331E

Hello,

The following message appears in our TSM server log frequently now. This
occurs on an input tape in our remote pool during the remotepool's
(tapepool) Reclamation. I usually do a audit volume xxxxx fix=yes and
that takes care of the damaged file(s) on that tape but the issue comes
right back on a different tape.



ANR1330E The server has detected possible corruption in an object being
restored or moved. The actual values for the incorrect frame are: magic
53454652 hdr version 0002 hdr length  0032 sequence number 00000381 data
length 00000000 server id 00000000 segment id 0091556997627906 crc
00200000.

ANR1331E Invalid frame detected.  Expected magic 53454652 sequence
number 00000381 server id 00000000 segment id 0000000006387883.

ANR1330E The server has detected possible corruption in an object being
restored or moved. The actual values for the incorrect frame are: magic
53454652 hdr version 0002 hdr length  0032 sequence number 00000349 data
length 00000000 server id 00000000 segment id 60002793965424476
48 crc 0000015D. (PROCESS: 996)

ANR1331E Invalid frame detected.  Expected magic 53454652 sequence
number 00000349 server id 00000000 segment id 0000000006169139.
(PROCESS: 996)

I search the Archives and didn't actually find and satisfactory answer.
Other than damaged files?
Has anyone had this issue occur.



TSM 5.1.3.4
RS/6000 AIX 5.2


Thanks for any reply's in Advance!

<Prev in Thread] Current Thread [Next in Thread>