commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Bodewig (JIRA)" <>
Subject [jira] [Commented] (COMPRESS-194) Unable to create a TAR file that contains an entry which is >8 GB in size.
Date Tue, 10 Jul 2012 04:37:35 GMT


Stefan Bodewig commented on COMPRESS-194:

I don't know which dialect of tar Winrar supports, but I'd rather expect it to support POSIX/PAX
than STAR.  In fact it is possible it doesn't support either.  The same is true for right-clicking
on Windows (I didn't know it would support tar at all).

If I was you I'd try POSIX and if that fails research if either of your targets supports tars
with entries bigger than 8GB at all - and if so which dialect they want to speak.

> Unable to create a TAR file that contains an entry which is >8 GB in size. 
> ---------------------------------------------------------------------------
>                 Key: COMPRESS-194
>                 URL:
>             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
>            Reporter: jessy
>            Priority: Critical
>             Fix For: 1.4
>         Attachments: tarImplntion.txt
> The common-compress-1.4.1 api says it supports unlimited file sizes for tar and untar
operations. []
> 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(
> 	at org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.failForBigNumbers(
> 	at org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.putArchiveEntry(
> Looking for a fix .. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message