[
https://issues.apache.org/jira/browse/COMPRESS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved COMPRESS-194.
-------------------------------------
Resolution: Not A Problem
Fix Version/s: 1.4
The docs of Ant's compress Antlib are not exactly Commons Compress' docs ;-)
If you want to create archives with big files you have to explicitly enable it
by setting bigNumberMode to something other than
TarArchiveOutputStream.BIGNUMBER_ERROR (which is the default), i.e. you have to
chose between posix and star modes.
In the case of the Compress Antlib it means you have to chose a format that
supports big files in the tar task, i.e. "star", "gnu" or "posix".
> Unable to create a TAR file that contains an entry which is >8 GB in size.
> ---------------------------------------------------------------------------
>
> Key: COMPRESS-194
> URL: https://issues.apache.org/jira/browse/COMPRESS-194
> Project: Commons Compress
> Issue Type: Bug
> Components: Archivers
> Affects Versions: 1.4.1
> Environment: I am using win xp and Red HatLinux 5.1v, but this should
> be platform independent.
> Reporter: jessy
> Priority: Critical
> Fix For: 1.4
>
>
> The common-compress-1.4.1 api says it supports unlimited file sizes for tar
> and untar operations. [http://ant.apache.org/antlibs/compress/]
> Only Untar operations on a file > 8GB is fixed,
> But creating a tar on a file >8GB is not working.
> When I try to do " tarOutputStream.putArchiveEntry(archiveEntry); "
> i get the below exception.
> java.lang.RuntimeException: entry size '9633985364' is too big ( > 8589934591
> )
> at
> org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.failForBigNumber(TarArchiveOutputStream.java:572)
> at
> org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.failForBigNumbers(TarArchiveOutputStream.java:557)
> at
> org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.putArchiveEntry(TarArchiveOutputStream.java:297)
> Looking for a fix ..
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
