Tar Archive Issues

Cyber-DL · 06-20-2009, 04:56 AM

I have same problem ,

so i think it's about 32bit and 64bit os !

i used VPS , and this events is on vps ,
my OS is CentOS x64 , but a thing it's appear , my previous vps was : CentOS x64 and backups stored in a CentOS , 32bit via FTP backup , and now i want restore it in CentOS x64 in my new VPS , and i don't have access to my previous vps ,
at last :

account was in a Centos x64 and stored in a CentOS 32bit via FTP backup , and now i transfered backups ( was stored & created in a 32 bit centos ) to my new vps with centos x64 and i want restore them !

so what's your idea ?

Note :
i used tar tvzf files.tar.gz and gzip -d files.tar.gz , and i see the same error

Code:

tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers

gunzip: files.tar.gz: invalid compressed data--crc error

gunzip: files.tar.gz: invalid compressed data--length error
tar: Error exit delayed from previous errors

Please HElp ME

gd2shoe · 06-22-2009, 12:37 AM

This is a different problem, and really does not belong in this thread.

You are getting CRC checksum errors and length errors. I'm going to go out on a limb and say that your file is bad and was probably truncated. You may not have finished downloading it from your VPS. Is the file as big as you expected it to be?

After some experimentation, I suspect you have a very small file that should have been much bigger. (assuming it really didn't list any filenames) I doubt you have recoverable data. My sympathies.

(And for the record, Base64 has nothing to do with running a 64 bit OS. Email attachments have been encoded that way for many years, regardless of the systems they originated on. Apparently some versions of tar used Base64 way back when. Hence: "obsolescent base-64 headers")

tgp1994 · 11-26-2009, 09:49 PM

I had a problem very similar to this. I was trying to unarchive binutils on Base Linux, when it was giving me the errors described in the first post. Simply doing what ashishdugar described above seemed to work. (However, I had to switch some of the tar switches around.) Be warned that tar is VERY picky about where you put its switches! For example, saying tar -fx samplearchive.tar will not work, because x must come before f.

Pit · 12-10-2010, 06:11 PM

Quote:

Originally Posted by Cyber-DL

I have same problem ,

so i think it's about 32bit and 64bit os !

i used VPS , and this events is on vps ,
my OS is CentOS x64 , but a thing it's appear , my previous vps was : CentOS x64 and backups stored in a CentOS , 32bit via FTP backup , and now i want restore it in CentOS x64 in my new VPS , and i don't have access to my previous vps ,
at last :

account was in a Centos x64 and stored in a CentOS 32bit via FTP backup , and now i transfered backups ( was stored & created in a 32 bit centos ) to my new vps with centos x64 and i want restore them !

so what's your idea ?

Note :
i used tar tvzf files.tar.gz and gzip -d files.tar.gz , and i see the same error

Code:

tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers

gunzip: files.tar.gz: invalid compressed data--crc error

gunzip: files.tar.gz: invalid compressed data--length error
tar: Error exit delayed from previous errors

Please HElp ME

Obvisouly, better not to use the param "--force" when doing rpmbuild.
It worked for me!

XavierP · 12-11-2010, 08:35 AM

I have split the new questions off into this thread.

XavierP · 12-11-2010, 10:41 AM

Thread closed as it was long dead before I messed around with it.