Bug 64968
Summary: | cpio doesn't work with large files | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | David Stevenson <d.j.stevenson> |
Component: | cpio | Assignee: | Peter Vrabec <pvrabec> |
Status: | CLOSED DUPLICATE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | bnocera, jcdiomar, neal.hamlin, paulm, pcfe, stuart |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:48:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Stevenson
2002-05-15 08:45:51 UTC
cpio has been built with large file support in 7.3. Bug is reproduceable with Red Hat Linux 7.3 with cpio-2.4.2.-26 and under Phoebe 2, with cpio-2.5.-1. Please can you tell me when this problem will be resolved as we have around 25 unix platforms using cpio and have restore scripts built around this program. This bug has already been fixed on Red Hat Linux 8.0 and 9, you can recompile the source RPMs from these versions onto the release you are using. I grabbed both the 2.4.2-28 and 2.5-3 source RPM for cpio and re-compiled it on a RH7.3 box using: rpmbuild --rebuild cpio-<ver>.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/cpio-<ver>.i386.rpm and both versions returned the same error: /bin/cpio: ./bigfile: Value too large for defined data type Next thing to look at? File was just over 3GB in size, using: find . -mount -print0 | /bin/cpio -0 -H newc -o -C 10240 -O /dev/nst0 I got same error on fedora core 1 (with a 4G file) This is an old bug- any hope for some attention? *** This bug has been marked as a duplicate of 105617 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |