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

bugzilla at busybox.net bugzilla at busybox.net
Fri Feb 21 13:06:30 UTC 2014


https://bugs.busybox.net/show_bug.cgi?id=6908

--- Comment #1 from Denys Vlasenko <vda.linux at googlemail.com> 2014-02-21 13:06:30 UTC ---
(In reply to comment #0)
> I have a directory on Android which has one file of 3+GB and the other three
> files that are much smaller.
> 
> I am trying to transfer the directory from the Android (from shell) to the BSD
> box. For this purpose I run this command:
> tar cf - my-directory | ssh user at host "cd /somedir && tar xf -"

What "tar --help" says? (Is it bbox's tar? Which version?)

> What I observe:
> Command succeeds, nothing is printed.
> Only two files are left on the BSD box in /somedir/my-directory
> One smaller file went first and is transferred correctly.
> 3+GB file has the right size, but the contents are damaged (md5 hash mismatch)
> Two other files failed to transfer.
> 
> 3+GB file on destination grew gradually to ~1.3GB, after which it quickly grew
> to the right size. hexdump shows that after 1.3GB the file contains only zeros.

Can you run " tar cf - my-directory | hexdump -C | tail -n100000"
and show the (part of) the output where file data ends and zeros start?
(The "part of" should be large - NOT three lines! more like 300 or more
lines around the problematic part)

-- 
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