Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!sgi!shinobu!odin!anchor!olson
From: olson@anchor.esd.sgi.com (Dave Olson)
Newsgroups: comp.sys.sgi
Subject: Re: bru/Exabyte read failures
Message-ID: <1991Jun7.204132.1856@odin.corp.sgi.com>
Date: 7 Jun 91 20:41:32 GMT
References: <1991Jun6.151002.31286@kuhub.cc.ukans.edu>
Sender: news@odin.corp.sgi.com (Net News)
Organization: Silicon Graphics, Inc.  Mountain View, CA
Lines: 27

In <1991Jun6.151002.31286@kuhub.cc.ukans.edu> arritt@kuhub.cc.ukans.edu writes:

| We just got a brand-new Exabyte drive from a company called
| R-Squared.  The tapes seem to write fine, but the problem
| comes in reading them back.  I've done two backups using 'bru'
| and get no write errors.  But I've tried to list the tape contents
| using
|     bru -tv > brulog.exabyte.060691
| and get the following error messages after the tape is partially read:
|     bru: warning - assuming end of volume 1 (unknown size)
|     bru: load volume 2 and enter device [default: /dev/tape]
| i.e., the system seems to erroneously think it's reached the
| end of the media???
| 
| The error appears to be non-systematic, i.e. successive attempts
| get the error at different places on the tape (200 MB into the
| tape, 400 MB, right near the beginning, whatever).

I would check to see if there are any messages in /usr/adm/SYSLOG
that would shed more light on the problem.  If there are none,
then there is likely to be something wrong with the drive, with
it reporting a FM or EOD when it shouldn't.
--

	Dave Olson

Life would be so much easier if we could just look at the source code.