From owner-freebsd-questions@FreeBSD.ORG Sun Dec 5 07:39:21 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 478E216A4CE for ; Sun, 5 Dec 2004 07:39:21 +0000 (GMT) Received: from lakeshore.hc.ti.com (adsl-68-95-186-60.dsl.rcsntx.swbell.net [68.95.186.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4CC643D54 for ; Sun, 5 Dec 2004 07:39:20 +0000 (GMT) (envelope-from pf@lakeshore.hc.ti.com) Received: from lakeshore.hc.ti.com (localhost.hc.ti.com [127.0.0.1]) by lakeshore.hc.ti.com (8.12.11/8.12.11) with ESMTP id iB57dHo2001143; Sun, 5 Dec 2004 01:39:17 -0600 (CST) (envelope-from pf@lakeshore.hc.ti.com) Received: (from pf@localhost) by lakeshore.hc.ti.com (8.12.11/8.12.11/Submit) id iB57dH7M001140; Sun, 5 Dec 2004 01:39:17 -0600 (CST) (envelope-from pf) Date: Sun, 5 Dec 2004 01:39:17 -0600 (CST) Message-Id: <200412050739.iB57dH7M001140@lakeshore.hc.ti.com> From: Paul Fuqua To: freebsd-questions@freebsd.org Subject: IDE Tape Trouble on 4.10: Volume Overflow X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 07:39:21 -0000 I have an IDE tape drive, a Seagate STT20000A TR-5, which I have used for backups with FreeBSD 3.4, 4.3, and 4.7. I have a script that dumps all my partitions, one after the other, and depends on "dump -a" to notice end-of-tape and prompt me to switch tapes. I just moved up to 4.10 -- doing a reinstall, not an update -- and now "dump -a" isn't detecting end-of-tape. Instead, dump reports a write error and there is a console message: /kernel: ast0: WRITE - VOLUME OVERFLOW asc=0x00 ascq=0x02 error=0x02 Is this a known problem? What can I do about it? (Aside from hacking my script to use "dump -B" and "mt rdhpos" to work around it, which is mostly functional but not entirely satisfactory.) I have tried building a kernel with "device atapicam" and using /dev/sa0 instead of /dev/ast0, but for some reason writing to /dev/sa0 doesn't actually write anything to the tape, even though I can probe the tape and move it around with mt. (But that's another problem, or perhaps some setup is needed that I haven't figured out yet.) Relevant dmesg output: ast0: TAPE at ata1-slave PIO4 sa0 at ata1 bus 0 target 1 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 16.000MB/s transfers I'd appreciate any suggestions. Thanks. pf