Tiny Core Linux

Tiny Core Base => TCB Bugs => Topic started by: andyj on July 25, 2013, 08:15:26 AM

Title: Busybox xz truncates files larger than 60M
Post by: andyj on July 25, 2013, 08:15:26 AM

A large file, say an eglibc-2.17 source tarball, is about 12M compressed, and about 120M when fully uncompressed. Uncompressing it with busybox xz results in a truncated file. Is this a Busybox issue, or is there some system parameter that limits this?

Andy

Title: Re: Busybox xz truncates files larger than 60M
Post by: curaga on July 25, 2013, 08:19:44 AM

If you have enough free space, please test busybox git, and if it still happens, report to busybox.

edit: The kernel tarball unpacks fine, it's 66mb compressed and 471mb uncompressed.

Title: Re: Busybox xz truncates files larger than 60M
Post by: gerald_clark on July 25, 2013, 08:48:26 AM

Your filesystem is in RAM, so unless you are uncompressing to mounted persistent storage, you may just be running out of RAM.

Title: Re: Busybox xz truncates files larger than 60M
Post by: tinypoodle on July 25, 2013, 09:24:36 AM

What are your sizes of RAM and of swapspace?

Title: Re: Busybox xz truncates files larger than 60M
Post by: andyj on August 05, 2013, 08:42:25 AM

It's a VM with a gig of RAM, no swap. 8 gig HD. Linux source unxz | untar worked OK, now that you mention it. xzcat eglibc-2.17 | tar xv gives a "tar: short read". Slackware unxz's the file OK, using the non-busybox xz. Something about the way the file was compressed?

Andy

Title: Re: Busybox xz truncates files larger than 60M
Post by: bmarkus on August 05, 2013, 08:57:40 AM

Did you try xz from the repo on the same file in the same system?

Title: Re: Busybox xz truncates files larger than 60M
Post by: andyj on August 07, 2013, 12:16:02 PM

Maybe it was an "available memory" thing, because I can't reproduce it now.