Bug 7889 - /bin/cpio fails to write tapes properly
/bin/cpio fails to write tapes properly
Status: CLOSED DUPLICATE of bug 6376
Product: Red Hat Linux
Classification: Retired
Component: cpio (Show other bugs)
6.1
All Linux
medium Severity medium
: ---
: ---
Assigned To: bero
http://danvi.vi
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-12-19 06:23 EST by danvi
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-12-19 12:41:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description danvi 1999-12-19 06:23:22 EST
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 12:41:59 EST
*** 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.