When backing up files on a DAT drive I go to the directory where the
files are located then give the command:
find . -depth -print | cpio -ovB > /dev/st0
The DAT tape (on an HP SureStore DAT8 drive) does write to the tape
and goes merrily on its way until the task is completed. With a false
sense of security, one puts the tape on read-only and stores it.
The shock comes when extacting the files by going to the directory
where they are to be written and issuing the command:
cpio -ivBdm < /dev/st0
Interspersed between each file message is the message:
skipped 28 bytes of junk
skipped 2746 bytes of junk
and similar messages. Some of the files are restored ok; some are
restored corrupted; and others are missing in their entirety.
I note that the 6.1 version of /bin/cpio is only about 48k while
other versions are over 292k. By writing DAT tapes with an earlier
version (or the SCO version) one gets a good, restorable tape.
*** This bug has been marked as a duplicate of 6376 ***