commons-issues mailing list archives

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


David Wartell - R1Soft commented on COMPRESS-16:

I had same problem.

I found this fellow that has really figured it out.  He has added what appears to be full
GNU tar support to the ice.tar package.

FYI ice tar was the original public domain source that ant's tar support was adapted from

!! Attaching a patch against ant 1.7.1 that supports GNU tar extension. !!  It Would be REALLY
REALLY nice to at least get this patch incorporated into  ant!  Thanks!

It was huge priority for me to have support for > 8GB files.  So I added only that element
of GNU tar.  

If you go the link above you can get a patched version of ice tar from him here:

This fellow Dan Mayer looks to have added full GNU support including multi-part tar files
and verification.  Since ANT tar is very similar to ice tar which was its ancestor it should
be feasible to port all of his work to ant's tar.

-David Wartell

> unable to extract a TAR file that contains an entry which is 10 GB in size
> --------------------------------------------------------------------------
>                 Key: COMPRESS-16
>                 URL:
>             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
> 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:
> unexpected EOF with 24064 bytes unread
> 		at
> 		at org.apache.commons.compress.archivers.tar.TarInputStream.copyEntryContents(
> 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.

View raw message