Operating System - HP-UX
1819934 Members
3421 Online
109607 Solutions
New Discussion юеВ

cpio..... > 2GB. Not dumped

 
OLIVA_1
Regular Advisor

cpio..... > 2GB. Not dumped


Hello,

I have an error with cpio when I try ton backup some files :

frrou01:(/oracle/P30/sapdata1)(root)#find /oracle/P30/sapdata1 -name el620d.data1 | cpio -o > /oracle/P30/sapdata1/romu
"/oracle/P30/sapdata1/el620d_1/el620d.data1": Value too large to be stored in data type
cpio: Size of /oracle/P30/sapdata1/el620d_1/el620d.data1 > 2GB. Not dumped.
1 blocks
frrou01:(/oracle/P30/sapdata1)(root)#

I have installed this cpio version :
http://hpux.cs.utah.edu/hppd/hpux/Gnu/cpio-2.6/

The cpio command above runs whitout error. But my cpio command is lanched through a SAP binary and it doesn't work properly with GNU cpio version...

Someone knows if it exists a HP PATCH or something like that ?

Thanks,
6 REPLIES 6
OLIVA_1
Regular Advisor

Re: cpio..... > 2GB. Not dumped

The SAP command I use is "brbackup"....
Antonio Cardoso_1
Trusted Contributor

Re: cpio..... > 2GB. Not dumped

Hi,

do you have the "largefiles" option in lvol /oracle/P30/sapdata1/romu ?
fsadm /

Steven E. Protter
Exalted Contributor

Re: cpio..... > 2GB. Not dumped

Shalom,

Two possible issues:

1) cpio version is old and can't make files bigger than 2 GB. HP has an enhancement that permits up to 8 GB in the patch database.

2) Filesystem not largefile enabled.

Two ways to fix that:
destructive newfs -F vxfs -o largefiles
fsadm as shown above. This method is non-destructive.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
OLIVA_1
Regular Advisor

Re: cpio..... > 2GB. Not dumped

Hello Steven,

What is the patch which HP's enhancement that permits cpio up to 8 GB in the patch database ?


Thanks,
OLIVA_1
Regular Advisor

Re: cpio..... > 2GB. Not dumped

Steven,

- My cpio version is recent and it is manage files bigger than 2 GB.

- Filesystem is largefile enabled.

My error is provided bu brbackup SAP command:

BR226I Rewinding tape volume in device /dev/rmt/3m ...

BR351I Restoring /oracle/P30/sapbackup/.tape.hdr0
BR355I from /dev/rmt/3mn ...
BR278E Command output of 'LANG=C cd /oracle/P30/sapbackup && /usr/sap/P30/SYS/exe/run/brtools -f detach LANG=C cpio -iumdvcBR .tape.hdr0 < /dev/rmt/3mn':
cpio: .tape.hdr0: invalid group


Thanks,
Bill Hassell
Honored Contributor

Re: cpio..... > 2GB. Not dumped

HP's cpio is still limited to a maximum file size of 2Gb (see the man page warnings). This is due to industry standards. HP did provide supply a patch for tar which increases the maximum file size to 8Gb but a tape with files larger than 2Gb on it cannot be read by unpatched tar or on other platforms -- in other words, not portable.

Largefiles are enabled because the file you are trying to backup is larger than 2Gb, so that option is not a concern. It would only be a concern if the destination was not a tape drive but a file on a disk.

Now adding the GNU versin of cpio does not replace the HP-supplied version of cpio. If you read the Installation notes, the GNU cpio program is installed in /usr/local and this path is normally not in the standard PATH for users. When your backup script says: "cpio", there is no way to locate cpio without consulting $PATH. The first occurance of cpio will likely be /usr/bin which is the HP version.

So the first error message (>2Gb not dumped) means that the HP version of the program is still being used. The second error message: ".tape.hdr0" means that cpio does not understand what this means. So you'll need to correct the command line, as well as change cpio to the correct pathname, probably /usr/local/bin/cpio.

NOTE: /usr/local has historically shipped with bad permissions (777) and should not be used for important programs until all the directories below /usr/local are changed to 755. Most of the install instructions for the open source programs from HP's IE (Internet Express) packages state this problem and suggest changing the permissions. 777 is a very dangerous permission for a directory because all programs and directories can be removed and removed by anyone.


Bill Hassell, sysadmin