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

bugzilla at busybox.net bugzilla at busybox.net
Thu Feb 20 07:18:59 UTC 2014


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

           Summary: tar is broken on Android: resulting stream produces
                    damaged files when unpacked
           Product: Busybox
           Version: unspecified
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: critical
          Priority: P5
         Component: Other
        AssignedTo: unassigned at busybox.net
        ReportedBy: yuri at tsoft.com
                CC: busybox-cvs at busybox.net
   Estimated Hours: 0.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 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.

Using command:
cat large-file | ssh user at host "cat > large-file"
transfers file correctly.

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