Am Donnerstag, den 16.06.2005, 07:59 -0500 schrieb Martin McCormick:
> tar zxf otherfilesystem/root.tar.gz, things seemed to start for a
> while and then disaster!!!
>
>
> gzip: stdin: unexpected end of file
> tar: Read 4489 bytes from /mnt/root.tar.gz
Some days ago I had a similar problem.
tar
On Fri, Jun 17, 2005 at 12:35:55AM +0200, Almut Behrens wrote:
> On Thu, Jun 16, 2005 at 07:59:09AM -0500, Martin McCormick wrote:
> >
> > gzip: stdin: unexpected end of file
> > tar: Read 4489 bytes from /mnt/root.tar.gz
> >
> > Apparently a special file or something in / makes gzip stop
>
Almut Behrens writes:
>I'm afraid your tarball got corrupted... In that case - I'm sorry to
>say - you're almost certainly outta luck. After creating a tar.gz
>file, the _whole_ tarfile has been piped through gzip, so if any part
>of the file gets corrupted afterwards (however tiny - a single bit
On Thu, Jun 16, 2005 at 07:59:09AM -0500, Martin McCormick wrote:
>
> gzip: stdin: unexpected end of file
> tar: Read 4489 bytes from /mnt/root.tar.gz
>
> Apparently a special file or something in / makes gzip stop
> before decompressing most of the 900 MB file. Is there any way to
> cause
before rebuilding a system after an upgrade that went terribly wrong,
I did the following in order to save kernel sources and configuration files:
tar cf - . |gzip >../otherfilesystem/root.tar.gz
This worked fine on the home file system and I recovered all
the /home files but when I went
5 matches
Mail list logo