You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Stefan Bodewig (JIRA)" <ji...@apache.org> on 2011/07/23 07:05:09 UTC

[jira] [Issue Comment Edited] (COMPRESS-124) Unable to extract a TAR file that contains sparse entries

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

Stefan Bodewig edited comment on COMPRESS-124 at 7/23/11 5:04 AM:
------------------------------------------------------------------

svn revision 1149798 and 1149799 hold the major part of Patrick's original patch, I've left out the doc changes for now and overridden canReadEntryData

      was (Author: bodewig):
    svn revision 1149798 holds the major part of Patrick's original patch, I've left out the doc changes for now and overridden canReadEntryData
  
> Unable to extract a TAR file that contains sparse entries
> ---------------------------------------------------------
>
>                 Key: COMPRESS-124
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-124
>             Project: Commons Compress
>          Issue Type: New Feature
>          Components: Archivers
>    Affects Versions: 1.1, 1.2
>         Environment: Platform independent. However, I'm currently using Window 7 Enterprise.
>            Reporter: Patrick Dreyer
>         Attachments: gnuSparseFile.patch
>
>
> Good news first: I already have the patch ready for that.
> I got several TAR files which I could not extract with any of the existing Java implementations, but I could extract all those TAR files successfully with GNU tar.
> It turned out that all the failing TAR files contained so called sparse files. Investigating the source code of all existing Java TAR implementations showed me that none of them even recognizes the existence of GNU sparse entries.
> Actually, I don't need to process one of the contained sparse files and I'm happy if I'm at least able to correctly untar all the non-sparsed files. Thus, it would be sufficient recognizing sparse files without the need to correctly un-sparse them while extracting. As long as all non-sparsed files get extracted correctly, I'm fine.
> The TAR files in question have all been VMware Diagnostic File bundles.
> See http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=653 to know how to get them.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira