Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!daffy!uwvax!uwm.edu!reuter.cse.ogi.edu!hp-cv!hp-pcd!hplabs!hplextra!news.dtc.hp.com!col.hp.com!canyon.sr.hp.com!darrylo
From: darrylo@sr.hp.com (Darryl Okahata)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: 2.0.5 tape blocksize???
Date: 15 Jun 1995 16:55:51 GMT
Organization: Hewlett-Packard / Center for Primal Scream Therapy
Lines: 21
Message-ID: <3rpomn$97r@canyon.sr.hp.com>
References: <3rja69$9fu@canyon.sr.hp.com> <3rm34s$3d4@marvin.gmd.de>
Reply-To: darrylo@sr.hp.com
NNTP-Posting-Host: mina.sr.hp.com
X-Newsreader: TIN [version 1.2 PL2]
Joachim Kaeber (kaeber@marvin.gmd.de) wrote:
> sysinstall uses cpio with the '-B' flag, so the blocksize is
> set to 5120 bytes. The following setup worked for me:
>
> tar cf - dir0 dir1 ... dirN | dd of=/dev/rst0 obs=5120
Thanks to everyone who replied -- the key was indeed the 5120-byte
blocksize. I ended up using the "-b" of tar to set the blocking size.
Out of curiousity, why is the tape buffer size in the default
kernel limited to under 10240-bytes? The default buffer size in tar is
20 blocks or 10240 bytes, and it's kinda silly to regen the kernel just
to use default blocking sizes with tar.
-- Darryl Okahata
Internet: darrylo@sr.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion or policy of Hewlett-Packard or of the
little green men that have been following him all day.