commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Dreyer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COMPRESS-124) Unable to extract a TAR file that contains sparse entries
Date Fri, 14 Jan 2011 08:11:45 GMT

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

Patrick Dreyer commented on COMPRESS-124:
-----------------------------------------

I have to thank that I could base my work on the existing implementation.
Actually, I was rather surprised about the high quality code. One doesn't find such fine crafted
open-source code each day. My compliments to all contributors!

Recognizing sparse files and reading their sparse blocks was not that hard, but correctly
writing such during exporting will be more complicated to to.
Thus, unfortunately I won't find the time to implement correct sparse file export and I'm
more than happy that I can at least kind of "skip" them.


> 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
>             Fix For: 1.2
>
>         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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message