ADSM-L

Re: 3570 errors continued

1998-11-09 07:32:39
Subject: Re: 3570 errors continued
From: "Garin P. Walsh" <Garin_Walsh AT NOTES.SABRE DOT COM>
Date: Mon, 9 Nov 1998 07:32:39 -0500
It might be a long shot but I have had it occur now twice in the last
month..... Check to see if the read/write tab is still on all the tapes.
What was happening to me, and it sounds similar, was that a database backup
was running and it had selected a tape that the r/w tab had popped off of.
It would mount it, generate an unable to mount error, put the bad tape back
in its slot, wait 60 seconds, and then try again (IBM support - could the
db backup code be modified to try a different tape in the event of a mount
failure?). Because the tab had popped off ADSM was unable to mount it for
write. It would bounce like this for a long time. While this was happening
I was getting mount failures on other processes because the "drive was
full" - near as I could tell, it was just because the db backup process
still owned the drive and hadn't released it. I did a checkout on the tape
and as soon as the db backup process mounted another tape the "full drive"
message went away and all was fine from then on.

If nothing else it is worth a shot.

Garin Walsh
The Sabre Group.




Pat Mills <Pat_Mills AT SONYMUSIC DOT COM> on 11/04/98 01:22:46 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: 3570 errors continued




We and IBM have been working on a 3570 problem for about 3 weeks now.  Of
course the first culprit is always microcode.

The level we are now running on 2 3570s is an unreleased version.

EC C70552
LINK D1I4_22F

Didn't fix my problem. But why would it? It works for a year then self
destructs? I don't think so.

One 3570 works the other doesn't. When I do a "audit libr LIB1", after it
reads the label on the second tape, doesn't matter what position that
second tape is in, and fails with a ANR8300E.
Description= The destination slot or drive was full in an attempt to move a
volume.

Hardware? Software? Hardware?...........

I'm beginning to think we'll never know.

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