From owner-freebsd-questions  Mon Jun 25 13:33:43 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from gandalf.cc.purdue.edu (gandalf.cc.purdue.edu [128.210.135.25])
	by hub.freebsd.org (Postfix) with ESMTP id 38B5737B401
	for <freebsd-questions@freebsd.org>; Mon, 25 Jun 2001 13:33:40 -0700 (PDT)
	(envelope-from jrj@gandalf.cc.purdue.edu)
Received: from gandalf.cc.purdue.edu (jrj@localhost [127.0.0.1])
	by gandalf.cc.purdue.edu (8.9.1/8.9.1) with ESMTP id PAA19601;
	Mon, 25 Jun 2001 15:33:32 -0500 (EST)
Message-Id: <200106252033.PAA19601@gandalf.cc.purdue.edu>
To: "Toomas Aas" <toomas.aas@raad.tartu.ee>
Cc: freebsd-questions@freebsd.org, amanda-users@amanda.org
Subject: Re: tape record too big for supplied buffer 
In-reply-to: Your message of "Mon, 25 Jun 2001 14:36:56 +0200."
             <200106251237.f5PCb8Y04792@lv.raad.tartu.ee> 
Reply-To: jrj@cc.purdue.edu
Date: Mon, 25 Jun 2001 15:33:31 -0500
From: "John R. Jackson" <jrj@gandalf.cc.purdue.edu>
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

>Generally everything seems to work fine, but sometimes I get these 
>messages in /var/log/messages:
>...
>Jun 20 09:57:00 kuller /kernel: (sa0:ahc1:0:6:0): 32768-byte 
>tape record bigger than suplied buffer

When do you get these errors?  When you're doing an amdump (i.e. writing
to the tape)?  When you're labeling a new tape?  When you're doing a
recovery (reading the tape)?  When you're running amcheck (which would
also be reading)?  What happens to whatever you're trying to do, i.e.
does Amanda fail in some way?

I think the message is saying some program gave the kernel a buffer that
was smaller than the record size reported by the drive (32 KBytes).

Amanda is extremely unlikely to have done that.  My first suspicion
would be a kernel or driver buffer management problem.  Maybe you could
ask those folks?

>Toomas

John R. Jackson, Technical Software Specialist, jrj@purdue.edu

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