string

tar: directory checksum error
Cause
This error message from tar(1) indicates that the checksum of the directory and the
files it has read from tape does not match the checksum advertised in the header
block. Usually this indicates the wrong blocking factor, although it could indicate
corrupt data on tape.
Action
To resolve this problem, make certain that the blocking factor you specify on the
command line (after -b) matches the blocking factor originally specified. If in doubt,
leave out the block size and let tar(1) determine it automatically. If that doesn’t
help, tape data could be corrupted.
tar: tape write error
Cause
A physical write error has occurred on the tar(1) output file, which is usually a
tape, although it could be a diskette or disk file. Look on the system console, where
the device driver should provide the actual error condition. This might be a
write-protected tape, a physical I/O error, an end-of-tape condition, or a file too large
limitation.
Action
In the case of write-protected tapes, enable the write switch. For physical I/O errors,
the best course of action is to replace the tape with a new one. For end-of-tape
conditions, try using a higher density if the device supports one, or use cpio(1) or
pax(1) for their multi-volume support. When encountering file too large limitations,
use the parent shell’s limit(1) or ulimit(1) facility to increase the maximum file
size.
See Also
For more information on tar tapes, see the section on copying UFS files in the System
Administration Guide, Volume I.
Alphabetical Message Listing 181