Yes, the input/out put error is standard when labeling a new "blank"
tape. However, this particular tape was labeled on one of the 4 drives
sometime ago. Which, I don't recall. The tape is no different than any
of the others as near as I can tell. Same batch, vendor, etc. Also, I
should note that is was labeled into the same pool as the others. The
problem is very strange. There are obviously a number of things one
could try:
1. Reboot both storage node (it manages the LTO library) and primary
server
2. Power cycle the LTO library
3. Clean the drive
3. Delete the volume and index entries and scan the tape, preferably on
the affected drive
I decided to do nothing as this appears to be an anomaly. I just
documented the problem so next time it happens, I'll be sure to check
my documentation to see why.
George
Vitaly Porotikov wrote:
>
> George,
>
> Did you try label this tape on /dev/nst2-4 devices? If the same result I
> guess this is wrong tape. Sometimes this kind of tapes appear among new
> tapes. Curiously, I could not label ANY blank tape with label 1N1001 (I used
> the label from our tape vendor and printed it by myself) in StorageTek L40
> with DLT8000.
> BTW, I get the same message "Tape label read: Input/Output error" if
> label any blank tape. I've read in Networker list before it should be
> ignored.
>
> --
> Yours, Vitaly Porotikov aka vp12929 on ws22a963
>
> Why is it that when you DIE, you can't take your HOME ENTERTAINMENT
> CENTER with you??
>
> George Sinclair wrote:
>
> > Okay, here's a weird one:
> >
> > I have an LTO (generation 1) volume that I am unable to successfully
> > inventory in one of my four LTO drives: /dev/nst5. These drives are
> > Seagates, first generation LTO in a StorageTek L80 attached to a Linux
> > Redhat 7.3 box.
> >
> > NetWorker loads the tape in the drive and gets to the point of:
> > "verifying label, rewinding" but just sits on that for a while before it
> > finally reports:
> >
> > "Tape label read: Input/Output error"
> >
> > and then ejects the tape. The tape is now reported as '_*' in the mount
> > listing.
> >
> > However, if I use any of the other three devices: /dev/nst2, 3 or 4 it
> > inventories like a champ. Now, here's the strange part. I tried
> > inventorying other tapes in
> > /dev/nst5, and they all work just dandy, but it will never inventory
> > that
> > one particular tape in /dev/nst5. I then checked the details on the
> > device and no consecutive errors are reported for /dev/nst5. nst5 seems
> > to function fine for everything else. Hmm ...
> >
> > Any thoughts? Maybe just clean the drive and re-try? Has anyone ever
> > seen this kind of behavior before?
> >
> > Thanks.
> >
> > George
> >
> > --
> > Note: To sign off this list, send a "signoff networker" command via email
> > to listserv AT listmail.temple DOT edu or visit the list's Web site at
> > http://listmail.temple.edu/archives/networker.html where you can
> > also view and post messages to the list.
> > =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
