Re: ADSM tape pool enters loop on tape write error

Rui Malheiro wrote:
>
> Hi all!
>
> I just can't figure why this can be possible:
>
> During an archive,
> 1. - Volume 1588MK reaches EOV
> 2. - SCRATCH volume 1588U6 is mounted and defined to the storage pool
> 3. - About 2 minutes later and error is found on volume 1588U6
> 4. - Volume 1588U6 is dismounted and marked readonly
>
> Now for the strange bit:
>
> 5. - Volume 1588U6 is deleted (and thus returned to SCRATCH)
> 6. - Volume 1588MK is mounted again
>
> And it loops to 1. and keeps repeating this over and over and over...
>
> Looking at it, what seems to be causing the problem is the volume being
> deleted and returned to scratch. Is this supposed to work like this? If so,
> why???
> Does anybody know if it can be worked around by seting REUSEDELAY?
>
> Environment and other info:
>
> AIX 3.2.5
> ADSM 2.1.5.6
> 3570 model B02
>
> [Extracted from the Activity Log]
> ANR8341I End-of-volume reached for 3570 volume 1588MK.
>
> ANR8336I Verifying label of 3570 volume 1588MK in drive RMT2 (/dev/rmt2).
>
> ANR8776W Volume 1588U6 in drive RMT3 (/dev/rmt3) contains lost VCR data;
> performance may be degraded.
>
> ANR8337I 3570 volume 1588U6 mounted in drive RMT3 (/dev/rmt3).
>
> ANR1340I Scratch volume 1588U6 is now defined in storage pool MENSAL.
>
> ANR8468I 3570 volume 1588MK dismounted from drive RMT2 (/dev/rmt2) in
> library 3570.
>
> ANR8302E I/O error on drive RMT3 (/dev/rmt3) (OP=WRITE, CC=0, KEY=04,
> ASC=44, ASCQ=00, Description=An undetermined error has occurred).  Refer to
> Appendix B in the 'Messages' manual for recommended action.
> ANR1411W Access mode for volume 1588U6 now set to "read-only" due to write
> error.
>
> ANR0523W Transaction failed for session 287 for node MAPPOR1 (AIX) - error
> on output storage device.
>
> ANR1341I Scratch volume 1588U6 has been deleted from storage pool MENSAL.
>
> ANR8337I 3570 volume 1588MK mounted in drive RMT2 (/dev/rmt2).
>
> ANR8468I 3570 volume 1588U6 dismounted from drive RMT3 (/dev/rmt3) in
> library 3570.
>
> ANR8341I End-of-volume reached for 3570 volume 1588MK.
>
> ANR8336I Verifying label of 3570 volume 1588MK in drive RMT2 (/dev/rmt2).
>
> ANR8776W Volume 1588U6 in drive RMT3 (/dev/rmt3) contains lost VCR data;
> performance may be degraded.
>
> ANR8337I 3570 volume 1588U6 mounted in drive RMT3 (/dev/rmt3).
>
> ANR1340I Scratch volume 1588U6 is now defined in storage pool MENSAL.
>
> ANR8468I 3570 volume 1588MK dismounted from drive RMT2 (/dev/rmt2) in
> library 3570.
>
> ANR8302E I/O error on drive RMT3 (/dev/rmt3) (OP=WRITE, CC=0, KEY=04,
> ASC=44, ASCQ=00, Description=An undetermined error has occurred).  Refer to
> Appendix B in the 'Messages' manual for recommended action.
> ANR1411W Access mode for volume 1588U6 now set to "read-only" due to write
> error.
>
> ANR0523W Transaction failed for session 287 for node MAPPOR1 (AIX) - error
> on output storage device.
>
> ANR1341I Scratch volume 1588U6 has been deleted from storage pool MENSAL.
>
> ANR8337I 3570 volume 1588MK mounted in drive RMT2 (/dev/rmt2).
>
> ANR8468I 3570 volume 1588U6 dismounted from drive RMT3 (/dev/rmt3) in
> library 3570.
>
> ANR8341I End-of-volume reached for 3570 volume 1588MK.
>
> [...]
> And so on...
>
> I wish a Happy New Year for all in this list.
>
> --
> Rui Malheiro,
> 6 Mil - Tecnologias de Informacao
> URL: <http://www.6mil.pt/>
Hi,
  I've had this happen a few times on ADSM 2.1.0.13 running on OS390R3.
I've opened an ETR with IBM, but it looks like the problem is with the
HSC Silo software.  I have a problem open with STK also.  I don't know
if you use a tape handling software or not, if not though, maybe the
problem is with ADSM.  Our situation is a little different.  The tape is
on the drive after being written to by ADSM (either a backup session
with a client or the migrate process), while the tape drive is waiting
for the mountretention period to expire, ADSM will dynamically allocate
the drive again and start writing to the tape volume.  ADSM then issues
the message 'ANR5335E Volume xxxxxx already used'.  It's like the tape
software doesn't recognize the JES3 keep for the tape.  Maybe there are
others on the list with similar problems?