[Bug 6908] tar is broken on Android: resulting stream produces damaged files when unpacked

bugzilla at busybox.net bugzilla at busybox.net
Mon Feb 24 01:42:14 UTC 2014


--- Comment #4 from Denys Vlasenko <vda.linux at googlemail.com> 2014-02-24 01:42:13 UTC ---
(In reply to comment #3)
> Created attachment 5246 [details]
> tail of the hex dump of the damaged tar archive
> Due to the attachment size limitations, I had to truncate to 2000 last lines.
> Hope this is still useful.

Hmm. I don't see anything obviously broken there.

It doesn't look like a case of "modulo 2Gb" bug: the file you are compressing
is 0xe36447c0 bytes,
the tarball is only 0x1c9bc080 bytes, nowhere near 0x636447c0.
It's also strange that tarball size isn't a multiple of 512 bytes!

> I can upload the whole huge.tar if this would help.

You can do that indeed, but it will be much smaller if your source file is
easily compressible instead of random. (File contents is not likely to be the
cause of the bug). Re-create it with the command

$ yes 1234567890abcde | dd bs=16 count=$((3815000000/16)) >huge

so that the file is a repeating sequence of 16 bytes "1234567890abcde\n",
then tar it up, bzip2 it (it will be small), and attach the file here.

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

More information about the busybox-cvs mailing list