mark@umcp-cs.UUCP (11/24/83)
Directory checksum could mean that the tape is bad.
But in actual practice on our machine it almost always means
that the reading and writing blocking factors are not the same.
The most usual blocking factors are 1 and 20.
This will give you a blocking factor of 1 (replace rmt12 with your
favorite tape physical device):
tar tfb /dev/rmt12 1
This a blocking factor of 20:
tar tfb /dev/rmt12 20
--
spoken: mark weiser
UUCP: {seismo,allegra,brl-bmd}!umcp-cs!mark
CSNet: mark@umcp-cs
ARPA: mark.umcp-cs@CSNet-Relaygwyn%brl-vld@sri-unix.UUCP (11/25/83)
From: Doug Gwyn (VLD/VMB) <gwyn@brl-vld> Assuming your "tar" works correctly, "directory checksum error" usually means you have tried to read a non-tar archive or the archive has gotten corrupted somehow.
Ttang.uci-750a%rand-relay@sri-unix.UUCP (11/30/83)
I am not sure which Unix system you are using, however on 4.1xbsd, tar used to calculate and store a checksum for each header block written on the tape. The message "directory checksum error" might be produced when you are trying to read a header that represents a directory and there are some errors thus cause an incorrect checksum. /ttang
alpert@inmet.UUCP (12/10/83)
#R:mb2c:-19500:inmet:9200002:000:444
inmet!alpert Dec 2 11:35:00 1983
I got this error just the other day and was completely confounded
until I noticed that the tape was labeled as 800 BPI...
-- Bob Alpert
-- Intermetrics, Inc.
733 Concord Ave.
Cambridge, MA 02138
...harpo!inmet!alpert
...hplabs!sri-unix!cca!ima!inmet!alpert
...yale-comix!ima!inmet!alpert
...uw-beav!cornell!esquire!inmet!alpert