Q: tar blocking factor/blocksize

Q: tar blocking factor/blocksize

Post by Travis Hassloch x2 » Wed, 20 Mar 1996 04:00:00



I'm not really sure to post this, I hope it's relevant.
The NetBSD-specific part is at the bottom.

My problem is that I don't understand blocking factors.

I know how to use tar to increase it; no big whoop.  But how are blocks
delimited on the tape?  With an escape code, file header, or out of band
info?

How come when I gzcat and redirect to the raw tape device, Solaris tar
complains "blocksize=2"?  How does it know, and how can I set it?  Do I
have to pipe thru cpio or dd or something?
--

WARNING: Unsolicited commercial e-mail: $500 per message
US Code, Title 47 Section 227 (http://www.law.cornell.edu/uscode/47/227.html)
This message may not be redistributed on the Microsoft Network.

 
 
 

Q: tar blocking factor/blocksize

Post by VAll » Thu, 21 Mar 1996 04:00:00



: I'm not really sure to post this, I hope it's relevant.
: The NetBSD-specific part is at the bottom.

: My problem is that I don't understand blocking factors.

: I know how to use tar to increase it; no big whoop.  But how are blocks
: delimited on the tape?  With an escape code, file header, or out of band
: info?

: How come when I gzcat and redirect to the raw tape device, Solaris tar
: complains "blocksize=2"?  How does it know, and how can I set it?  Do I
: have to pipe thru cpio or dd or something?
: --

: WARNING: Unsolicited commercial e-mail: $500 per message
: US Code, Title 47 Section 227 (http://www.law.cornell.edu/uscode/47/227.html)
: This message may not be redistributed on the Microsoft Network.

I would like to expand on this question.  Many of the new streamer tapes
are "pre-formatted" (QIC-80, QIC-WIDE, and others).  Can anyone provide
info on the block sizes for these tapes?

Clayton Valley


 
 
 

Q: tar blocking factor/blocksize

Post by John McGrat » Fri, 22 Mar 1996 04:00:00



> I know how to use tar to increase it; no big whoop.  But how are blocks
> delimited on the tape?  With an escape code, file header, or out of band
> info?

I am not certain how things work on many of the new tape drives, but I can tell
you how things used to work on 9 track reel-to-reel tapes (and 7 track if you
remember those).  But I suspect that the concepts have not changed much.

What is generally called a "block" when talking about tape writing software is
called a "record" when dealing with the tape controller.  This is the smallest
unit that can be read or written.  The controller writes "records" to the tape,
separated by Inter-Record Gaps.  It can also write "tape marks", which are often
used to delimit files.  Two successive tape marks without intervening records
indicates the end-of-tape.

It is interesting to note that the Inter-Record Gaps were physically rather
large, approximately 3/4 of an inch.   This meant that the record (block) size
had a rather profound effect on tape capacity.  On a 6250 bpi drive, 80 byte
records would occupy 80/6250 = 0.128 inches.  With a 3/4 inch gap between each
record, this meant that the tape held 1.7% data and 98.3% Inter-Record Gap.

-- John McGrath

 
 
 

1. SCO tar error on block size (not block factor)

Someone recommended:
tar cvfb - ./config 32768 | compress | dd of=/dev/rmt/0m bs=32k  
tar: invalid blocksize. (Max 20)
0+1 records in
0+1 records out

Seeing his/her error i supposed that what they meant was the actual
block
size in bytes to match the 'dd' record size.  But
tar cvfB -  ./config 32768  | compress | dd of=/dev/rmt/0m bs=32k
tar: B: unknown option
Usage: tar -{txruc}[0-9vfbkelmnopwAFLTP] [tapefile] [blocksize]
[tapesize] files...
        Key     Device            Block   Size(K)    Tape
        0       /dev/rfd048ds9    18      360        No    
        1       /dev/rfd148ds9    18      360        No    
        2       /dev/rfd096ds15   10      1200       No    
        3       /dev/rfd196ds15   10      1200       No    
        4       /dev/rfd0135ds9   18      720        No    
        5       /dev/rfd1135ds9   18      720        No    
        6       /dev/rfd0135ds18  18      1440       No    
        7       /dev/rfd1135ds18  18      1440       No    
        8       /dev/rct0         20      0          Yes    
        9       /dev/rctmini      20      0          Yes    
        10      /dev/rdsk/fp03d   18      720        No    
        11      /dev/rdsk/fp03h   18      1440       No    
        12      /dev/rdsk/fp03v21 10      20330      No  

Is there a way to get tar to match the 'dd' record size please?
--

have
access to a news server; thanks!
Disclaimer: opinions expressed my own and not representative of my
employers

2. Perl Tute

3. tar tape blocking factor

4. Automount problems

5. tar blocking factor

6. redhat 6.1 hangs after install

7. Best tar blocking factor for HP DDS tape drive ?

8. ms-windows wallpaper washout

9. How do I determine the optimal blocking factor for tar?

10. block size vs. blocking factor

11. DAT blocking factor & tapetool

12. DDS3, ufsdump, blocking factor.

13. tape blocking factors