commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Bodewig (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (COMPRESS-16) unable to extract a TAR file that contains an entry which is 10 GB in size
Date Wed, 07 Dec 2011 12:16:40 GMT


Stefan Bodewig resolved COMPRESS-16.

       Resolution: Fixed
    Fix Version/s: 1.4

writing such entris has been split out as COMPRESS-165.

With svn revision 1211405 I have added tests that prove the tar package now understand both
the star/GNU/BSD variant as well as the POSIX/PAX one.
> 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
>          Components: Archivers
>         Environment: I am using win xp sp3, but this should be platform independent.
>            Reporter: Sam Smith
>             Fix For: 1.4
>         Attachments: 0001-Accept-GNU-tar-files-with-entries-over-8GB-in-size.patch, 0002-Allow-creating-tar-archives-with-files-over-8GB.patch,
0004-Prefer-octal-over-binary-size-representation.patch, 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:
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message