So far all the symptoms you described in the previous messages point to
misconfiguration of device files vs. robot positions.
Make sure that you have the drive device nodes mapped to the correct slots in
the robot.
For example:
# sgscan
/dev/sg/c0t7l0: Changer: "ATL P3000 6310050"
/dev/sg/c0t7l1: Tape (/dev/rmt/0): "QUANTUM DLT7000"
/dev/sg/c0t7l2: Tape (/dev/rmt/1): "QUANTUM DLT7000"
/dev/sg/c0t7l3: Tape (/dev/rmt/2): "QUANTUM DLT7000"
/dev/sg/c0t7l4: Tape (/dev/rmt/3): "QUANTUM DLT7000"
Should then correspond to your device definitions in NetBackup, such that
/dev/rmt/0 is robot drive 1
/dev/rmt/1 is robot drive 2
/dev/rmt/2 is robot drive 3
/dev/rmt/3 is robot drive 4
etc.
>From all the evidence, you are mounting the tapes in one drive and trying to
>read / write a different one. That is why you get I/O errors on same tapes in
>different drives...
Peter
-----Original Message-----
From: danix AT cloud9 DOT net [mailto:danix AT cloud9 DOT net]
Sent: Thursday, 23 May 2002 1:56
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] more on drives being downed
I'm learning.
I looked in /opt/openv/netbackup/db/media/errors and found a bunch of read
errors.
I parsed the file with grep/cut/sort/uniq and came up with around 22 different
tapes that present read errors, all since May 14th, a few days before we
made our original system changes.
So, it seems that netbackup is doing the right thing and marking the drives
as down, when it is seeing the read errors.
So, now we are:
- increasing the logging levels
- checking the storagetek array (9710) for hardware problems.
- going to try new tapes
It's hard to believe that 20+ tapes are all bad, and it's also not a coincidence
that both arrays were having problems. Could there be something at the Sun
level causing read errors? In my experience, read errors are either bad
tapes or bad heads.
To answer a couple of other questions I received, we've run robtest OK, we don't
have a separate media server, and we're reinventoried the robot (actually
reinstalled 4.3 completely yesterday).
I'm pointing to hardware problems at this point, how about you?
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This message is for the named person's use only. It may contain sensitive and
private proprietary or legally privileged information. No confidentiality or
privilege is waived or lost by any mistransmission. If you are not the intended
recipient, please immediately delete it and all copies of it from your system,
destroy any hard copies of it and notify the sender. You must not, directly or
indirectly, use, disclose, distribute, print, or copy any part of this message
if you are not the intended recipient. CREDIT SUISSE GROUP and each legal
entity in the CREDIT SUISSE FIRST BOSTON or CREDIT SUISSE ASSET MANAGEMENT
business units of CREDIT SUISSE FIRST BOSTON reserve the right to monitor all
e-mail communications through its networks. Any views expressed in this message
are those of the individual sender, except where the message states otherwise
and the sender is authorized to state them to be the views of any such entity.
Unless otherwise stated, any pricing information given in this message is
indicative only, is subject to change and does not constitute an offer to deal
at any price quoted. Any reference to the terms of executed transactions should
be treated as preliminary only and subject to our formal written confirmation.
|