From owner-freebsd-questions  Wed Apr 19 18:50:29 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id SAA08348
          for questions-outgoing; Wed, 19 Apr 1995 18:50:29 -0700
Received: from genesis.tiac.net (genesis.tiac.net [204.180.76.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA08336
          for <questions@freebsd.org>; Wed, 19 Apr 1995 18:50:26 -0700
Received: by genesis.tiac.net (8.6.9/genesis0.0)
	id VAA17244; Wed, 19 Apr 1995 21:50:21 -0400
Date: Wed, 19 Apr 1995 21:50:21 -0400
From: steve2@genesis.tiac.net (Steve Gerakines)
Message-Id: <199504200150.VAA17244@genesis.tiac.net>
To: questions@FreeBSD.org
Subject: Re: QIC-80 for backups - is this right?
Sender: questions-owner@FreeBSD.org
Precedence: bulk

> Well, personally I've never been a big fan of these tapes drives (I've
> definately had problems with them).  However, the problem you describe
> sounds a heck of a lot like you hit a bad spot on the tape and the
> driver just keeps rewriting over and over.  Are you running V1.1.5.1
> or V2.0R?  Version 2 is much better at handling this type of thing...
> with V1 the driver had the annoying habit of just sitting there forever
> and ever trying to write the tape.

This problem still exists in the current version of the driver, although
it happens less frequently than earlier versions.  The way to recover
from such a thing is to have the driver realize that this is a bad block
and then automatically update the bad sector map.  Once the bad sector map
is updated you need to recalculate error correction and then re-write
the tape segment, skipping over the newly marked bad spot.

Because error correction is currently outside the driver it is
impossible to recover.  I'm re-doing the driver now and this is one
feature it'll have.

> The solution.  Believe it or not I find that reformatting the tape (yup,
> spending 2 hours doing it) with the DOS based formatting program (none
> available under FreeBSD :-( will generally fix the problem.  This will
> reestablish the bad block map and generally set things up pretty well.

That usually solves it, but not without a re-boot or yanked tape first. :-(

- Steve
steve2@genesis.tiac.net