Bug 246003 - CPIO error writing to tape on files larger than 7gb.
Summary: CPIO error writing to tape on files larger than 7gb.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: cpio
Version: 4.5
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Radek Brich
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-27 20:09 UTC by Ron Angel
Modified: 2008-07-28 04:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-06-29 11:41:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ron Angel 2007-06-27 20:09:49 UTC
Description of problem:
CPIO error writing to tape on files larger than 7gb. We have 2 large files in
our backup:  The first file is 7gb in size and the other is 35gb in size.  cpio
generates errors on both files. I removed the first file and it then resulted
with the same error on the second file.

"cpio -oc --block-size=16MB >/dev/st0 </file_list"


Version-Release number of selected component (if applicable):
cpio-2.5-13.RHEL4

How reproducible:
This has occurred daily using a script.  The specific script portion using cpio
is noted in step one below.  The "file_list" is a flat file from a find command.


Steps to Reproduce:
1.cpio -oc --block-size=16MB >/dev/st0 </file_list
2."cpio field width not sufficient for storing file size" results on the large files
3. Backup runs a few more minutes and then hits the "end of tape" too soon
  
Actual results:


Expected results:


Additional info:

Comment 1 Radek Brich 2007-06-29 11:41:35 UTC
Size of files stored in cpio archive is limited to 4 GiB. Larger files are skipped.

You can use another archive type, like tar, which supports files up to 64 GiB.

Comment 2 Andrew Furey 2008-07-28 04:24:26 UTC
From the source it looks like it was part of the writeOutHeaderBufferOverflow patch.

I'm reverting to cpio-2.5-9.RHEL4 for now, as it has no such limit. Why was this
changed? 4 GiB seems to be a horribly low limit for an archive tool...


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