Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

gzip, unexpected end of file

1,723 views
Skip to first unread message

dave

unread,
Aug 27, 2003, 2:24:37 PM8/27/03
to
Hello,
I've got a gzipped tarball, created on an rh9 machine that i'm trying to
extract. Unfortunately, i keep getting an error from gzip: unexpected end of
file. And of course tar immediately fails as well. What i need to do is find
a howto on repairing this file, in some way or having gzip ignore this error
and continue, or extract around the errors, i need to get the information
out of this tarball.
Any help appreciated.
Thanks.
Dave.


Kris Kennaway

unread,
Aug 27, 2003, 4:00:09 PM8/27/03
to

The gzip is corrupted or truncated. You should be able to extract up
to the damaged portion by extracting to stdout with the -c option.
Continuing beyond the error is impossible because gzip is a stream
format.

Kris

dave

unread,
Aug 27, 2003, 9:09:41 PM8/27/03
to
Hello,
Thank you, i will try this. Is there another method of backup that would
not involve this problem? This is the first time it has happened when making
a tarball. I believe that dump is file system specific, that would not work
in this case.
Thanks.
Dave.


Lori A. Kargl

unread,
Aug 27, 2003, 11:43:09 PM8/27/03
to

"dave" <dmeh...@woh.rr.com> wrote in message
news:FH63b.19282$l41.3...@twister.neo.rr.com...

How did you get the tarball onto your FreeBSD machine? It seems
that you used ftp in ASCII mode instead of binary mode. Can you
transfer the file again? Can you extract the tarball on a rh9
machine?

--
steve


dave

unread,
Aug 28, 2003, 9:56:03 AM8/28/03
to
Hello,
I was given an ext3 formatted drive with this rather large file on it. I
used cp to get it from the readonly drive on to my fbsd box then i extracted
it. I'm trying to find an rh9 machine to put this drive into to try
extracting it there, but i'm not sure if this will work.
Thanks.
Dave.


Kris Kennaway

unread,
Aug 28, 2003, 10:00:04 AM8/28/03
to
In article <pDc3b.19372$l41.3...@twister.neo.rr.com>, dave wrote:
> Hello,
> Thank you, i will try this. Is there another method of backup that would
> not involve this problem?

One would presume so, since file corruption is not the normal
condition. You need to identify what is causing the
truncation/corruption and make it stop.

* Did any errors occur during the file creation?

* Are any other files becoming corrupted on the system (possible
hartdware/software failure?)

* Was the file corrupted during transfer from the system, perhaps due
to transferring via FTP in ascii mode, or similar?

* Etc.


Kris

0 new messages