Re: [ADSM-L] Inconsisent behavior of mount errors on scratch tapes.

On Feb 27, 2009, at 8:44 , Steven Harris wrote:

Hi Gang

Case 1.

02/26/2009 04:16:48  ANR8944E Hardware or media error on drive DRIVE1
                     (\\.\Tape2) with volume DIA142L3(OP=TESTREADY,
Error
                     Number= 23, CC=0, KEY=03, ASC=53, ASCQ=00,


---8<---


Case 2.
02/24/2009 03:01:22  ANR8300E I/O error on library LTOCV1
(OP=00006C03,
CC=207,
                     KEY=05, ASC=21, ASCQ=01,
SENSE=70.00.05.00.00.00.00.0
A.0-
                     0.00.00.00.21.01.00.C0.00.06.,
Description=Device is
not
                     in a state capable of performing request).
Refer to
                     Appendix C in the 'Messages' manual for
recommended
                     action. (SESSION: 7658)
more...   (<ENTER> to continue, 'C' to cancel)

02/24/2009 03:01:22  ANR8779E Unable to open drive , error number=2.
(SESSION:
                     7658)
02/24/2009 03:01:22  ANR8300E I/O error on library LTOCV1
(OP=00006C03,
CC=207,
                     KEY=05, ASC=21, ASCQ=01,
SENSE=70.00.05.00.00.00.00.0
A.0-
                     0.00.00.00.21.01.00.C0.00.04.,
Description=Device is
not
                     in a state capable of performing request).
Refer to


---8<----

Questions.

Why did the first case not mark the tape Private?  Why did the
second case
retry the mount repeatedly on the same drive rather than moving on
to the
next one?


Because TSM assumed it was the media (wrongly so, but maybe because in
80%+ of the cases they get this error, it is the media at fault) in
the second case. In the first case TSM has never been able to even
read the label on the tape, so to TSM the tape might not be at fault.

As to TSM drive selection policy, yes, who knows why it selects which
drive? There was probably more going on on the lib?

Does anyone understand this behavior?

Thanks

Steve

Steven Harris
TSM Admin, Sydney Australia


--
Met vriendelijke groeten,

Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622