From owner-freebsd-current Thu Dec 26 11:21:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA04252 for current-outgoing; Thu, 26 Dec 1996 11:21:09 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA04246 for ; Thu, 26 Dec 1996 11:21:02 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id LAA28364; Thu, 26 Dec 1996 11:15:56 -0800 (PST) Message-ID: <32C2CEAD.794BDF32@whistle.com> Date: Thu, 26 Dec 1996 11:14:53 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Joerg Wunsch CC: FreeBSD-current users Subject: Re: DAT: reading with blocksize=256K References: <199612261827.TAA03226@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Heikki Suonsivu wrote: > > > I have been able to read my old backups written with 1024k blocksize. They > > secret was to use ddd instead of dd. > > This must be unrelated to the other problem. If they were written > with 1024 K blocksize on a FreeBSD machine, they were actually written > with 64 KB instead. The limit is in physio(9) (UTSL), and could not > be changed by whatever trickery from a userland program. > OR the drive is in fixed block mode. in FIXED block mode what is actually written to tape is fixed blocks and many are written at a time for a large read/write thus you can read and write differnt blocksizes because it always ends up a multiple of hte smaller blocksize anyway.. julian