From owner-freebsd-questions  Tue Jun 26 19: 4:26 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from mail.cs.ait.ac.th (mail.cs.ait.ac.th [192.41.170.16])
	by hub.freebsd.org (Postfix) with ESMTP id 23CA237B401
	for <freebsd-questions@freebsd.org>; Tue, 26 Jun 2001 19:04:23 -0700 (PDT)
	(envelope-from on@cs.ait.ac.th)
Received: from banyan.cs.ait.ac.th (on@banyan.cs.ait.ac.th [192.41.170.5])
	by mail.cs.ait.ac.th (8.11.3/8.9.3) with ESMTP id f5R26Zp52894;
	Wed, 27 Jun 2001 09:06:36 +0700 (ICT)
Received: (from on@localhost)
	by banyan.cs.ait.ac.th (8.8.5/8.8.5) id JAA15679;
	Wed, 27 Jun 2001 09:04:20 +0700 (ICT)
Date: Wed, 27 Jun 2001 09:04:20 +0700 (ICT)
Message-Id: <200106270204.JAA15679@banyan.cs.ait.ac.th>
X-Authentication-Warning: banyan.cs.ait.ac.th: on set sender to on@banyan.cs.ait.ac.th using -f
From: Olivier Nicole <on@cs.ait.ac.th>
To: toomas.aas@raad.tartu.ee
Cc: freebsd-questions@freebsd.org, amanda-users@amanda.org
In-reply-to: <200106251237.f5PCb8Y04792@lv.raad.tartu.ee>
	(toomas.aas@raad.tartu.ee)
Subject: Re: tape record too big for supplied buffer
References:  <200106251237.f5PCb8Y04792@lv.raad.tartu.ee>
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-questions.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-questions>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-questions>
X-Loop: FreeBSD.ORG

>I am using amanda 2.4.2p1 on FreeBSD 4.3. The tape drive is (from 
>dmesg):
>---
>sa0 at ahc1 bus 0 target 6 lun 0
>sa0: <HP C1537A L708> Removable Sequential Access SCSI-2 device sa0:
>10.000MB/s transfers (10.000MHz, offset 15)
>---
>Jun 20 09:57:00 kuller /kernel: (sa0:ahc1:0:6:0): tape is now 
>frozen-use an OFF LINE, REWIND or MTEOM command to clear this 
>state.
>---

Hi,

This is known to happen with FreeBSD.

I noticed it only happened on the first command run on one mounted
tape (and so far only on amlabel for me). Only way to solve it is to
do "mt offline" and start again. I tried to minimize the risk by
training my staff to do an amcheck once they loaded a new tape. That
way, if it must fail, it'll fail on the amcheck, not on the amdump.

It COULD be a dirty drivre, as it did not happen to me for long time,
since I do clean the drive once a week.

Olivier

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message