commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Wartell - R1Soft (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (COMPRESS-16) unable to extract a TAR file that contains an entry which is 10 GB in size
Date Mon, 04 May 2009 15:53:31 GMT

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

David Wartell - R1Soft edited comment on COMPRESS-16 at 5/4/09 8:53 AM:
------------------------------------------------------------------------

Patch for ant 1.7.1 to add support for WRITING entries > 8GB+ per GNU tar

      was (Author: wartelld):
    Patch for ant 1.7.1 to add 8GB+ file support per GNU tar
  
> 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
>             Fix For: 1.1
>
>         Attachments: ant-8GB-tar.patch
>
>
> 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