We face a very serious problem using CPIO.
find erp s3 -print|cpio -ocvB > /u/download/bu/erp.cpio 2>&1
gzip erp.cpio
So far, so good.
The server is based on Red Hat ES5.4. Version of cpio: cpio (GNU cpio) 2.6
Last week the server died, and we build exactly the same Linux-server, in a virtual environment.
During restore, we face several problems.
1. When typing 'file <cpio-file>' the answer is: data (nad not: cpio-archive)
2. When restoring:
cpio: warning: skipped 225 bytes of junk
The restore is aborted (far too early) with the message:
*** glibc detected *** cpio: free(): invalid next size (fast): 0x0933a298 ***
======= Backtrace: =========
/lib/libc.so.6[0xa42585]
/lib/libc.so.6(cfree+0x59)[0xa42959]
cpio[0x804b55a]
cpio[0x804ba2c]
cpio[0x804bff3]
cpio[0x8050cb1]
/lib/libc.so.6(__libc_start_main+0xdc)[0x9eee9c]
cpio[0x8049ac1]
======= Memory map: ========
00139000-0013b000 rw-p 00139000 00:00 0
00889000-00894000 r-xp 00000000 fd:00 7603490 /lib/libgcc_s-4.1.2-20080825.so.1
00894000-00895000 rw-p 0000a000 fd:00 7603490 /lib/libgcc_s-4.1.2-20080825.so.1
009bb000-009d5000 r-xp 00000000 fd:00 7603452 /lib/
ld-2.5.so009d5000-009d6000 r--p 00019000 fd:00 7603452 /lib/
ld-2.5.so009d6000-009d7000 rw-p 0001a000 fd:00 7603452 /lib/
ld-2.5.so
009d9000-00b18000 r-xp 00000000 fd:00 7603467 /lib/
libc-2.5.so00b18000-00b1a000 r--p 0013f000 fd:00 7603467 /lib/
libc-2.5.so
00b1a000-00b1b000 rw-p 00141000 fd:00 7603467 /lib/
libc-2.5.so00b1b000-00b1e000 rw-p 00b1b000 00:00 0
00c0d000-00c0e000 r-xp 00c0d000 00:00 0 [vdso]
08048000-08061000 r-xp 00000000 fd:00 1736709 /bin/cpio
08061000-08062000 rw-p 00019000 fd:00 1736709 /bin/cpio
09336000-09357000 rw-p 09336000 00:00 0 [heap]
b7da2000-b7fa2000 r--p 00000000 fd:00 20123766 /usr/lib/locale/locale-archive
b7fa2000-b7fa4000 rw-p b7fa2000 00:00 0
bf7f3000-bf808000 rw-p bffea000 00:00 0 [stack]
Aborted
We tried several things to solve this:
* Trying several levels of gunzip
* trying several options of cpio (block-size, format, with/without -c, etc.)
Can you give us a hint how to solve this? We are desperate, and our customer in panic.
Many thanks for your help in advance!
--