ADSM-L

Re: Access set to "unavailable".

1998-05-11 12:57:04
Subject: Re: Access set to "unavailable".
From: "Mapes, Mark" <MWM4 AT PGE DOT COM>
Date: Mon, 11 May 1998 09:57:04 -0700
Trevor,

thanks for the reply.

I should have stated that we are version 3.1.1 ADSM.  Our current
atldd.driver is 3.1.5.0 and our atape.driver is 4.1.3.0.

We started having problems after upgrading both AIX (from 3.2 to 4.2) and
ADSM (2.1), back in January.  We have applied upgraded ATAPE and ATLDD and
3490 micro code, as well as the latest fixes to ADSM, but the problems do
not go away (but they seem to transform into others).  One of the
frustrating problems is not knowing where the problem resides.  Is it ADSM
or 3494 or AIX or what?  Unfortunately, within IBM, these are all separate,
and ADSM is the only one showing any errors, as the error logs in AIX and
3494 do not show any corresponding errors.

Mark


> ----------
> From:         Trevor Foley[SMTP:Trevor.Foley AT BANKERSTRUST.COM DOT AU]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Sunday, May 10, 1998 6:46PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Access set to "unavailable".
>
> Hi Mark,
>
> We had a number of problems with tapes being put into strange tapes
> after the microcode was updates on our 3590s some time back. But it only
> affected our ADSM V3 server, not the V2 servers, even though the same
> level of microcode was applied. We fixed ours by upgrading to a later
> version of Atape. I know that you said that you are using 3490s, rather
> than 3590s, but it might help. We are now running Atape 4.1.3.0 and
> Atldd 3.1.2.0.
>
>
>
> Trevor
> ------------------------------------------------------------------------
> ------------------------------------------------
> Trevor Foley
> Bankers Trust Australia Limited
> Phone: 61-2-9259 3944    Fax: 61-2-9259 2659
>
>
>         -----Original Message-----
>         From:   Mapes, Mark [SMTP:MWM4 AT PGE DOT COM]
>         Sent:   Friday, May 08, 1998 5:33 AM
>         To:     ADSM-L AT VM.MARIST DOT EDU
>         Subject:        Access set to "unavailable".
>
>         Hello,
>
>         we have been getting this problem (see excerpt of activity log
> below, last
>         three messages is the problem) for several weeks, almost daily
> and the
>         frequency is increasing.  Any ideas?  Server is RS/6000 with
> SCSI attached
>         3490s and a 3494.
>
>            TIME     MESSAGE
>
>         --------
>
> ------------------------------------------------------------------------
> ----
>
> ------------------------------------------------------------------------
> ----
>
> ------------------------------------------------------------------------
> ----
>         ----------------------
>         00:34:17     ANR8337I CARTRIDGE volume 500174 mounted in drive
> 3490DR03
>         (/dev/rmt3).
>
>         00:39:03     ANR8325I Dismounting volume 500174 - 1 minute mount
> retention
>         expired.
>
>         00:39:04     ANR8336I Verifying label of CARTRIDGE volume 500174
> in drive
>         3490DR03 (/dev/rmt3).
>
>         00:39:30     ANR8468I CARTRIDGE volume 500174 dismounted from
> drive 3490DR03
>         (/dev/rmt3) in library 3494DCPP01.
>
>         02:51:11     ANR8337I CARTRIDGE volume 500174 mounted in drive
> 3490DR01
>         (/dev/rmt1).
>
>         03:01:00     ANR8325I Dismounting volume 500174 - 1 minute mount
> retention
>         expired.
>
>         03:01:02     ANR8336I Verifying label of CARTRIDGE volume 500174
> in drive
>         3490DR01 (/dev/rmt1).
>
>         03:01:28     ANR8468I CARTRIDGE volume 500174 dismounted from
> drive 3490DR01
>         (/dev/rmt1) in library 3494DCPP01.
>
>         03:01:34     ANR8782E Volume 500174 could not be accessed by
> library
>         3494DCPP01.
>
>         03:01:34     ANR1402W Mount request denied for volume 500174 -
> volume
>         unavailable.
>
>         03:01:34     ANR1410W Access mode for volume 500174 now set to
>         "unavailable".
>
>
>         Thanks.
>
>         Mark Mapes
>         PG&E
>
<Prev in Thread] Current Thread [Next in Thread>