From owner-freebsd-questions Wed Feb 20 21:58:57 2002 Delivered-To: freebsd-questions@freebsd.org Received: from lists.blarg.net (lists.blarg.net [206.124.128.17]) by hub.freebsd.org (Postfix) with ESMTP id 0F81537B400 for ; Wed, 20 Feb 2002 21:58:54 -0800 (PST) Received: from thig.blarg.net (thig.blarg.net [206.124.128.18]) by lists.blarg.net (Postfix) with ESMTP id 92DE2BD69 for ; Wed, 20 Feb 2002 21:58:53 -0800 (PST) Received: from localhost.localdomain ([206.124.139.115]) by thig.blarg.net (8.9.3/8.9.3) with ESMTP id VAA32059 for ; Wed, 20 Feb 2002 21:58:52 -0800 Received: (from jojo@localhost) by localhost.localdomain (8.11.6/8.11.3) id g1L613c01870; Wed, 20 Feb 2002 22:01:03 -0800 (PST) (envelope-from swear@blarg.net) To: freebsd-questions@freebsd.org Subject: Blocks and compression and SCSI tape drives From: swear@blarg.net (Gary W. Swearingen) Date: 20 Feb 2002 22:01:02 -0800 Message-ID: Lines: 39 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just got a HP SureStore 6000 external (Model C1529F) correctly (according to HP web site) reported as HP C1533A by the kernel. (It cost me 1O dollars -- the price of a tape! Seems to work too.) I've written a big file to it with the DCLZ compression (which it's supposed to have) enabled with "mt" and again with that disabled and "mt rdhpos" and "mt rdspos" show the same number of blocks written with compression on or off. Is this the way it's supposed to be? I would think that "hpos" ought to be blocks on the tape period, so that fewer blocks would be used with compression on, but either I'm not controlling compression or "blocks" are some kind of virtual thing and I'll have more tape blocks with compression on than off. What's the story? The "mt status" doesn't show block size. Do I have to experiment and fill the tape to determine what the block size is? What's with these "mt"-reported "hpos" and "spos" blocks? What's the diff, besides "hardware" and "software"? I guess I'm going to have to use these to position the tape, since the driver won't keep track of file position like it does with my TR-4 cartridge SCSI drive. What does "mt" mean by a "setmark". Of what use are they? Can I harm a DDS-2 DAT by doing "cat /dev/zero >/dev/tape"? I'm thinking of doing that and trying to see the block position at the end of the tape. If I've got the drive set for variable block size can I even use "cat", or must I use "dd" to limit the block size. What would that limit be? Is there any tradeoffs to using variable or fixed block sizes on the drive. Can "fixed" be used when using an archiver like "tar" which has it's own block size? Do they have to be equal or integer multiples? P.S. Know of any documentation on this stuff, other than the "mt" man page and the little handbook entry on 4mm drives? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message