From owner-freebsd-current Mon Sep 14 15:41:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09209 for freebsd-current-outgoing; Mon, 14 Sep 1998 15:41:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ducky.net (gate.ducky.net [198.145.101.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09195 for ; Mon, 14 Sep 1998 15:40:52 -0700 (PDT) (envelope-from mike@ducky.net) Received: (from mike@localhost) by ducky.net (8.9.1/8.8.5) id PAA13542 for current@freebsd.org; Mon, 14 Sep 1998 15:40:05 -0700 (PDT) Date: Mon, 14 Sep 1998 15:40:05 -0700 (PDT) From: Mike Haertel Message-Id: <199809142240.PAA13542@ducky.net> To: current@FreeBSD.ORG Subject: yow--"mt blocksize" eats tape! (SCSI, exabyte) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG using an exabyte 8505 tape drive, some time back under a 2.2.6 kernel, i made a backup by the following process: mt -f /dev/nrst0 blocksize 1024 tar cvf - /dev/nrst0 files-to-back-up | dd of=/dev/nrst0 obs=1m mt -f /dev/nrst0 offline (i used fixed blocksize 1024 tapes for compatibility with other operating systems, including UnixWare and Linux, and so i can do large block writes and still have small blocks on the tape.) apparently, however, "mt blocksize" has recently become a destructive operation! on a -current system, desiring to extract the tape, i did: [insert tape] mt -f /dev/nrst0 blocksize 1024 unlike what i used to see, this now takes a long time and causes some sort of tape activity. then: tar xvf /dev/nrst0 only to be greeted by an empty tape! apparently the "mt blocksize" command resulted in the tape being erased. i tried this again with another tape, the same thing happened. since when is "mt blocksize" destructive, and is this something that happened on purpose? Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message