Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 7889 - /bin/cpio fails to write tapes properly
Summary: /bin/cpio fails to write tapes properly
Status: CLOSED DUPLICATE of bug 6376
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: cpio
Version: 6.1
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: bero
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-12-19 11:23 UTC by danvi
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-12-19 17:41:12 UTC

Attachments (Terms of Use)

Description danvi 1999-12-19 11:23:22 UTC
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.

Comment 1 Jeff Johnson 1999-12-19 17:41:59 UTC
*** This bug has been marked as a duplicate of 6376 ***

Note You need to log in before you can comment on or make changes to this bug.