Roland,

I will make a stab at your problem.

If my memory serves me right (the old saying, "I got a great memory, but
its short!"), we too got a bunch of ANR8303Es, especially during heavy
drive usage.  The problem was the SCSI fast/wide controller was not
configured right.  Turns out that a valid card address are values 2-7(?) and
we had a value of 1.  If this is your problem, and you need more
nitty-gritty, we can compare our configurations.

Mark Mapes
PG&E

----------------------[Reply - Original Message]----------------------
Sent by:"Macuzzi, Roland" <macuro AT EDC3.EDC DOT CA>
Sent by:"Macuzzi, Roland" <macuro AT EDC3.EDC DOT CA>
 Hello:

I have a major problem with our tape reclamations in ADSM, and I've
seem
alot of good stuff
on this list so I thought that maybe(?) someone else may have been
through
this too.. {:-)
Here goes....

Intermittantly, only during tape reclamation processes, we get ANR8303E
errors (see below)
and consequently, the tape volume status' are set to Error-state and
Read-Only.
I wouldn't be so concerned except that it happens so regularly - several
times a week.
Periodically, I reset the tapes back to read-write (although this makes me
uncomfortable
as there may be a bonifide tape error among the bunch).
As I write this there are 29 tapes in error state because of this problem
(there are 200 in the tape storage pool) and at this rate I would be out of
tapes in the
not-too-distant future!
I'm basically sure it is not the tapes because they are all less than a year
old - and this
has been happening for awhile now, and the only tape operation where
this
error occurs
is tape reclamations.

We are in contact with IBM support on this because it is such a problem -
 - and according to their suggestion I'm trying to get a trace during an
actual error occurance
but I've tried and tried- unsuccessfully - -Somehow it knows when I'm
watching and
behave itself!  ARG!!! (I spent hours again last night - in futility)
 - not to mention performance is severely impacted while in "trace" mode
(testing is a slow,
time-consuming process and I'm running out of time...)

We are using an RS/6000 running AIX 4.1.4  as our ADSM server
(v2.1.5.6)
with our tape media
all being stored  in an IBM3494 Automatic Tape Library with two
3490E-C22's
installed.

Has anyone else experienced anything like this??

Any and all feedback is greatly appreciated!

Thanks
 --------------------------------------
Roland Macuzzi Email: macuro AT edc3.edc DOT ca

Sample Activity log:
=====================
Date/Time            Message
 --------------------
 ----------------------------------------------------------
....
07/17/1996 22:30:06  ANR8311E An I/O error occurred while accessing
drive
          TAPEDRIVE1 (/dev/rmt1).
07/17/1996 22:30:06  ANR8311E An I/O error occurred while accessing
drive
         TAPEDRIVE0 (/dev/rmt0).
07/17/1996 22:30:06  ANR1411W Access mode for volume E00001 now
set to
                      "read-only" due to write error.
07/17/1996 22:30:06  ANR1083W Space reclamation terminated for
volume E00010
 -
                      excessive read errors encountered.
07/17/1996 22:30:06  ANR1042I Space reclamation for storage pool
NEXTPOOL
will
                      be retried in 60 seconds.
07/17/1996 22:30:07  ANR8303E I/O error on drive TAPEDRIVE1
(/dev/rmt1)
                      (OP=LOADDISPLAY,

 SENSE=00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00-
                      .00.00.00.00.00.00.00.00.00.00.00.00.00.00.00).
07/17/1996 22:30:07  ANR8303E I/O error on drive TAPEDRIVE0
(/dev/rmt0)
                      (OP=LOADDISPLAY,

 SENSE=00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00-
                      .00.00.00.00.00.00.00.00.00.00.00.00.00.00.00).
07/17/1996 22:30:56  ANR8468I CARTRIDGE volume E00001 dismounted
from drive
                      TAPEDRIVE0 (/dev/rmt0) in library EDCLIB.
07/17/1996 22:31:06  ANR1043I Space reclamation retry delay ended;
checking
                      volume reclamation status for storage pool NEXTPOOL.
07/17/1996 22:31:06  ANR1040I Space reclamation started for volume
E00010,
                      storage pool NEXTPOOL (process number 5).
07/17/1996 22:31:06  ANR1044I Removable volume E00010 is required
for space
                      reclamation.
07/17/1996 22:31:06  ANR8324I CARTRIDGE volume E00010 is expected
to be
mounted
                      (R/O).
07/17/1996 22:31:15  ANR8468I CARTRIDGE volume E00010 dismounted
from drive
                      TAPEDRIVE1 (/dev/rmt1) in library EDCLIB.
07/17/1996 22:31:42  ANR8337I CARTRIDGE volume E00025 mounted in
drive
                      TAPEDRIVE2 (/dev/rmt2).
07/17/1996 22:32:07  ANR8337I CARTRIDGE volume E00010 mounted in
drive
                      TAPEDRIVE3 (/dev/rmt3).
07/17/1996 22:40:08  ANR8337I CARTRIDGE volume E00083 mounted in
drive
                      TAPEDRIVE0 (/dev/rmt0).
07/17/1996 22:40:31  ANR8337I CARTRIDGE volume E00082 mounted in
drive
                      TAPEDRIVE1 (/dev/rmt1).
07/17/1996 22:52:27  ANR8311E An I/O error occurred while accessing
drive
                      TAPEDRIVE2 (/dev/rmt2).
07/17/1996 22:52:27  ANR8311E An I/O error occurred while accessing
drive
                      TAPEDRIVE3 (/dev/rmt3).
07/17/1996 22:52:27  ANR1411W Access mode for volume E00025 now
set to
                      "read-only" due to write error.
07/17/1996 22:52:27  ANR1083W Space reclamation terminated for
volume E00010
 -
                      excessive read errors encountered.
07/17/1996 22:52:27  ANR1042I Space reclamation for storage pool
NEXTPOOL
will
                      be retried in 60 seconds.
.....

============================================================
=========
=========