Uploaded image for project: 'Commons Compress'
  1. Commons Compress
  2. COMPRESS-124

Unable to extract a sparse entries from tar archives

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.1, 1.2
    • Fix Version/s: 1.20
    • Component/s: Archivers
    • Labels:
    • Environment:

      Platform independent. However, I'm currently using Window 7 Enterprise.

      Description

      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.

        Attachments

        1. gnuSparseFile.patch
          21 kB
          Patrick Dreyer

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                patrickdreyer Patrick Dreyer
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 6.5h
                  6.5h