We had our 3494 library with two 3590 drives installed two years ago, and
for the first six months we were seeing failed drives at least twice a
week. In the end, it turned out that 3590 drives in a library need these
extra little things called 'locking clips' or something to hold the tapes
steady for the gripper to grab hold of them (stand alone 3590's do not need
these, something which should have occurred to the engineer much sooner
IMHO). As soon as each drive was fitted with one of these clips, we had no
more problems. This may not be your exact problem, but either way, we were
seeing the exact same effects. It sounds like a drive problem.
If you do want to do an audit, they are reasonably quick. We only have one
frame with approx 120 volumes in granted, but a minute or so does the job.
Farren Minns - John Wiley & Sons Ltd
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: audit library
On Friday, Jan 24, 2003, at 21:20 Australia/Sydney, Michelle Wiedeman
wrote:
> one of my drives in the library continues to produce errors and is
> taken
> offline by tsm.
> 01/24/03 11:00:45 ANR8779E Unable to open drive /dev/rmt1, error
> number=46.
> 01/24/03 11:00:51 ANR8792E Unrecoverable drive failures on drive RMT1
> (/dev/rmt1); drive is now taken offline.
> errno 46 is defined within aix as being a device not ready error.
>
> now I've tried to delete and redefine the unit on both platforms, but
> no
> success.
Both platforms? Is the drive being shared?
> the server no comes with an advice to audit the library, since I have
> no
> clues anymore I'm willing to try this, but have never done it before.
> The
> manuals speak of it as being quite time consuming but nowhere it says
> approx. how long and if I can in some way reduce the time.
> The manuals also state that some processes will be halted for as long
> as the
> audit is running, but again nowhere it states which ones or maybe all
> processes.
If this is a 3494 library, I've done several audits with no hassle.
Since
the 3494's library controller maintains a database of all the tapes
present
in the library, a TSM "audit library" just validates the libvolumes
table
against the library. It takes less than a minute.
BTW, if your drives are 3590s, I've seen problems like you describe
before.
For us, it was a combination of bad tapes, and old drive firmware. An
audit
library isn't going to help.
> does anyone have a clue??
I hope some of us do! :-)
Cheers,
--
Paul Ripke
Unix/OpenVMS/DBA
101 reasons why you can't find your Sysadmin:
68: It's 9AM. He/She is not working that late.
-- Koos van den Hout
|
