[ 
https://issues.apache.org/jira/browse/COMPRESS-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419651#comment-17419651
 ] 

chen commented on COMPRESS-589:
-------------------------------

[~ggregory] [~erans]

bro, I found the easiest way to display the problem.

first of all, We ran into this issue on an Android device
{code:java}
adb shell dd if=/dev/zero of=sdcard/test/1.mp4 bs=1024 count=102400
{code}
we can use the above adb command to construct 21 files which is 100M each under 
sdcard/test/. 

After using compress to tar the file, it is normal with 1.20, but 'Truncated 
TAR archive' occurs with 1.21 when we try to untar the file .

hope you guys can help me.

THX

 

> 1.21 throws a 'java.io.IOException: Truncated TAR archive' exception while 
> 1.20 not
> -----------------------------------------------------------------------------------
>
>                 Key: COMPRESS-589
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-589
>             Project: Commons Compress
>          Issue Type: Bug
>    Affects Versions: 1.21
>            Reporter: chen
>            Priority: Major
>
> the bug happens when I use the TarArchiveInputStream to read bytes from the 
> current tar archive entry.
> the trace shows as below
> {code:java}
> 08-27 14:39:18.657 10633 10963 W System.err: java.io.IOException: Truncated 
> TAR archive
> 08-27 14:39:18.657 10633 10963 W System.err: java.io.IOException: Truncated 
> TAR archive
> 08-27 14:39:18.657 10633 10963 W System.err: at 
> org.apache.commons.compress.archivers.tar.TarArchiveInputStream.getActuallySkipped(TarArchiveInputStream.java:478)
> 08-27 14:39:18.657 10633 10963 W System.err: at 
> org.apache.commons.compress.archivers.tar.TarArchiveInputStream.skipRecordPadding(TarArchiveInputStream.java:455)
> 08-27 14:39:18.657 10633 10963 W System.err: at 
> org.apache.commons.compress.archivers.tar.TarArchiveInputStream.getNextTarEntry(TarArchiveInputStream.java:367)
> {code}
> but when i downgrade to 1.20, the exception will not show again, so I think 
> it is a bug in the new version 
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to