ADSM-L

When a Drive Goes Missing?

2004-03-29 20:15:42
Subject: When a Drive Goes Missing?
From: Dwight McCann <dwight AT TRIXIE.ISC.UCSB DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 29 Mar 2004 17:14:01 -0800
I am running TSM 5.1.8.3 on Win2K with Overland Neo4100 fiber attached.
I had several sets of error messages like the following over the weekend
because one of the drives was not available during an improperly
performed power sequence and did not show up in the TSM Device Driver:

20040327063659  ANR8779E Unable to open drive mt1.2.0.5, error number=2.~
20040327063725  ANR8381E LTO volume TSM063 could not be mounted in drive 
MT1.2.0.5 (mt1.2.0.5).~
20040327063725  ANR1401W Mount request denied for volume TSM063 - mount failed.~

I am wondering why TSM even tried to put a tape in a drive that it knew
it did not have access to, and once it had tried and didn't have access,
why didn't it quite trying to use that drive over and over?  I would
have expected that using the TSM Device Driver would have (1) given me a
report that the drive was not available at boot and (2) would have
allowed TSM to know not to use a drive that was configured but was not
accessible.  Something like this should be so basic that an "enhancement
request" seems a bit absurd, so I am wondering if perhaps there is some
option that I need to enable to allow TSM to use information it already has?

--
Dwight McCann
Computer and Network Technologist, UCSB Info Systems & Computing
Dwight.McCann AT isc.ucsb DOT edu, Dwight AT DwightMcCann DOT com
http://borg.isc.ucsb.edu/dmm/  - office: 805-893-3113

<Prev in Thread] Current Thread [Next in Thread>
  • When a Drive Goes Missing?, Dwight McCann <=