Here's why we get VCR errors:

Date/Time            Message

--------------------
----------------------------------------------------------
----------------------------------------------------------
03/11/1999 02:51:31  ANR8337I 3590 volume M01372 mounted in drive I35905
03/11/1999 02:51:31  ANR8337I 3590 volume M01372 mounted in drive I35905

                      (/dev/rmt5).

03/11/1999 04:16:51  ANR8325I Dismounting volume M01372 - 1 minute mount

                      retention expired.

03/11/1999 04:16:53  ANR8336I Verifying label of 3590 volume M01372 in drive

                      I35905 (/dev/rmt5).

03/11/1999 04:18:00  ANR8468I 3590 volume M01372 dismounted from drive
I35905
                      (/dev/rmt5) in library IBM3494-01.

03/11/1999 09:43:39  ANR8337I 3590 volume M01372 mounted in drive I35906

                      (/dev/rmt6).

03/11/1999 09:43:57  ANR8330I 3590 volume M01372 is mounted R/W in drive
I35906
                      (/dev/rmt6), status: IN USE.

03/11/1999 09:45:57  ANR1157I Removable volume M01372 is required for Move
Data
                      process.

03/11/1999 09:45:57  ANR8324I 3590 volume M01372 is expected to be mounted

                      (R/W).

03/11/1999 10:02:22  ANR1411W Access mode for volume M01372 now set to

                      "read-only" due to write error.

03/11/1999 10:03:37  ANR8468I 3590 volume M01372 dismounted from drive
I35906
                      (/dev/rmt6) in library IBM3494-01.

03/11/1999 11:13:13  ANR8820W Repairing VCR data for Volume M01372 in drive

                      I35907 (/dev/rmt7); mount may be delayed.

03/11/1999 11:25:56  ANR8337I 3590 volume M01372 mounted in drive I35907

                      (/dev/rmt7).

03/11/1999 11:29:44  ANR8325I Dismounting volume M01372 - 1 minute mount

                      retention expired.

03/11/1999 11:30:53  ANR8468I 3590 volume M01372 dismounted from drive
I35907
                      (/dev/rmt7) in library IBM3494-01.

03/11/1999 13:47:34  ANR2232W This command will move all of the data stored
on
                      volume M01372 to other volumes within the same storage

                      pool; the data will be inaccessible to users until the

                      operation completes.

03/11/1999 13:47:51  ANR1157I Removable volume M01372 is required for Move
Data
                      process.

03/11/1999 13:47:51  ANR8324I 3590 volume M01372 is expected to be mounted

                      (R/O).

03/11/1999 13:47:51  ANR1140I Move data process started for volume M01372

                      (process ID 109).

03/11/1999 13:50:38  ANR8820W Repairing VCR data for Volume M01372 in drive

                      I35906 (/dev/rmt6); mount may be delayed.

03/11/1999 14:03:12  ANR8337I 3590 volume M01372 mounted in drive I35906

                      (/dev/rmt6).


So the deal is, the VCR data seems to have to get repaired everytime the
tape is mounted - and all this for a write error presumably at the very end
of the tape?

Jim
> ----------
> From:         Fred Johanson[SMTP:fred AT MIDWAY.UCHICAGO DOT EDU]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Thursday, March 11, 1999 1:03 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: your mail
>
> I determined, during a prolonged run of 3494 troubles, that the AIX
> message
> refers to the ADSM VCR repair message and is a nuissance and not a
> problem.
>  What is a problem is what causes the VCR loss.  My CE, who's great with a
> screwdriver, doesn't know.  One thing I never do, which may not have to do
> with anything other than paranoia, is bring down ADSM with a cartridge
> still in a drive.
>
>
>
>
>
> At 12:13 PM 3/11/99 -0500, you wrote:
> >On Thu, 11 Mar 1999, Purdon, James wrote:
> >
> >// Help! I am being plagued by a host of ANR8820Ws (Repairing VCR data
> for
> >// tapes on IBM 3590 drives).
> >//
> >// I hate these - the "repair" operation takes too long and doesn't
> always
> work
> >// (I've been waiting 10 minutes now for a repair to complete!).  And
> each
> >// incident seems to dump about four messages into the error log,
> claiming
> >// everything from the tape drive is broken (but the CEs say the drives
> pass
> >// all diagnostics) to that the drive is dirty (we clean each drive daily
> and
> >// our mount count isn't particularly high).
> >//
> >
> >I'm getting a similar condition only with a different error.
> >We have recently configured our new 3494 Lib. w/ 2 3590 drives using the
> >F/W Differential SCSI connect to an RS/6000 (AIX 4.2.1)
> >I'm getting constant "RECOVERY LOGIC INITIATED BY DEVICE" errors showing
> >up in the errpt on only one of the two tape drives.  Our CE has run
> >every diagnostic known to IBM and found nothing. The word from IBM is
> >"don't worry about it.  These errors aren't serious".  Any error
> >indicating recovery sounds serious to me... And what worries me the most
> >is that only one drive is giving the errors (likely eliminating a
> firmware
> >error or the like)  ADSM doesn't think there is anything wrong with the
> >drive, and hasn't shown any errors.  So I guess this isn't really
> helpful,
> >but I suppose it's possible the errors are in some way related in their
> >cause....
> >This help jog anyone's brain for ideas?
> >
> >TIA
> >
> >
> >-
> >Best regards,
> >Brian
> >
> >+-----------------------------------------------------------------------+
> >| Brian T. Huntley                              UNIX Systems Programmer |
> >| Campus Information Services, Clarkson University                      |
> >| Ph/FAX: 315.268-2292/6570                                             |
> >| bth AT clarkson DOT edu                                
> >www.clarkson.edu/~bth |
> >+-----------------------------------------------------------------------+
> > UNIX *is* user friendly. It's just selective about who its friends are.
> >        PGP Public Key available. finger bth AT clarkson DOT edu
> >
> Fred Johanson
> System Administrator, ADSM
> S.E.A.
> University of Chicago
> 773-702-8464
>