home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!kithrup!stanford.edu!agate!ames!sun-barr!olivea!sgigate!odin!fido!zola!zuni!anchor!olson
- From: olson@anchor.esd.sgi.com (Dave Olson)
- Newsgroups: comp.sys.hp
- Subject: Re: What is the default blocksize on HP DAT tapes ?
- Message-ID: <p6se2ls@zuni.esd.sgi.com>
- Date: 30 Aug 92 00:57:41 GMT
- References: <BtLL1z.HI7@news.cso.uiuc.edu>
- Sender: news@zuni.esd.sgi.com (Net News)
- Organization: Silicon Graphics, Inc. Mountain View, CA
- Lines: 31
-
- In <BtLL1z.HI7@news.cso.uiuc.edu> e-sink@uiuc.edu (Eric W. Sink) writes:
-
- | I'm writing 4mm DAT tapes on my Indigo, and reading them on HP's.
- | To get them to read on the HP, I have to set the blocksize to 256k
- | manually, since that is apparently the default blocksize for the
- | SGI, but the HP is something else. I would rather force the blocksize
- | on the SGI side, allowing the HP to read the tapes more easily. So,
- | what is the default blocksize for HP DAT tapes ?
- |
- | SGI:
- |
- | tar cvf - MYFILE | dd of=/dev/tape bs=?????
-
- My god, why would you do it like that! It complicates error
- recovery/handling , eats up CPU resources, and is probably slower.
-
- What is wrong with 'tar cvfb /dev/tape # MYFILE'? We default
- to 256 Kbytes (# == 512) if the b option is not specified when
- the drive is a DAT. That is half the size of the RAM buffer
- on the drive. By default, we write in variable block size, so
- you get 'blocks' that are actually 256 Kbytes. Some vendors
- hardware and/or drivers can't cope with that (Sun has to be
- less than 64 Kbytes - 2, at least, up through SunOS 4.1.X).
- Some versions of tar also have a maximum block size that they
- will tolerate. So the best thing to do is to simply choose
- a block size such that the machines you want to exchange tapes
- with can handle it.
- --
- Let no one tell me that silence gives consent, | Dave Olson
- because whoever is silent dissents. | Silicon Graphics, Inc.
- Maria Isabel Barreno | olson@sgi.com
-