commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COMPRESS-16) unable to extract a TAR file that contains an entry which is 10 GB in size
Date Wed, 02 Jun 2010 12:31:38 GMT

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

Sebb commented on COMPRESS-16:
------------------------------

There are other ways of supporting large files - e.g. PAX interchange format.

Compress needs to support reading large files as well - this is a bit simpler as far as the
API is concerned, because one can autodetect the format that has been used.

I agree that the output format needs to be configurable.

BTW, there are bugs in both the patches:
* GNU format sets only the high-order bit of byte[0] - not the whole byte
* The Javadoc is wrong, as it refers to parsing rather than formatting the number.

> unable to extract a TAR file that contains an entry which is 10 GB in size
> --------------------------------------------------------------------------
>
>                 Key: COMPRESS-16
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-16
>             Project: Commons Compress
>          Issue Type: Bug
>         Environment: I am using win xp sp3, but this should be platform independent.
>            Reporter: Sam Smith
>         Attachments: ant-8GB-tar.patch, patch-for-compress.txt
>
>
> I made a TAR file which contains a file entry where the file is 10 GB in size.
> When I attempt to extract the file using TarInputStream, it fails with the following
stack trace:
> 	java.io.IOException: unexpected EOF with 24064 bytes unread
> 		at org.apache.commons.compress.archivers.tar.TarInputStream.read(TarInputStream.java:348)
> 		at org.apache.commons.compress.archivers.tar.TarInputStream.copyEntryContents(TarInputStream.java:388)
> So, TarInputStream does not seem to support large (> 8 GB?) files.
> Here is something else to note: I created that TAR file using TarOutputStream , which
did not complain when asked to write a 10 GB file into the TAR file, so I assume that TarOutputStream
has no file size limits?  That, or does it silently create corrupted TAR files (which would
be the worst situation of all...)?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message