Date: Tue, 13 Apr 1999 07:19:25 -0700 (PDT) From: ben@algroup.co.uk To: freebsd-gnats-submit@freebsd.org Subject: kern/11112: Amanda on FreeBSD can wipe the _next_ tape! Message-ID: <19990413141925.2CC7314D0A@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 11112 >Category: kern >Synopsis: Amanda on FreeBSD can wipe the _next_ tape! >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 13 07:20:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Ben Laurie >Release: 2.2.8 >Organization: Apache Group >Environment: FreeBSD heap.ben.algroup.co.uk 2.2.8-RELEASE FreeBSD 2.2.8-RELEASE #0: Mon Nov 30 06:34:08 GMT 1998 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386 >Description: Using an HP JetStore 2000 (i.e. fairly standard DAT) and Amanda 2.4.1p1, if I manually eject the tape after a successful amdump run, insert a labelled tape and run amcheck, the check fails. It fails because the latter tape has been wiped! I suspect any command that operates on the tape will cause the same problem. I strongly suspect that this problem is associated with the "two filemarks" kludge in the tape drivers. >How-To-Repeat: See above. >Fix: Using "mt offline" instead of ejecting with the button on the tapedrive seems to avoid the problem. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990413141925.2CC7314D0A>