Bug 171625 - "invalid sparse archive member" when extracting tars
"invalid sparse archive member" when extracting tars
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: tar (Show other bugs)
4.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Vrabec
Ben Levenson
RHEL4U3NAK
:
Depends On:
Blocks: 187538
  Show dependency treegraph
 
Reported: 2005-10-24 11:17 EDT by Josh Kelley
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: RHBA-2006-0336
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-05-03 17:45:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Josh Kelley 2005-10-24 11:17:16 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

Description of problem:
Using tar to extract tar files created within Amanda often gives the following errors:
tar: ./filename: invalid sparse archive member
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers

This causes problems when restoring backups from Amanda.

This has been reported against Fedora Core in bug 143969 and bug 146314 but has not yet been fixed (as far as I can tell) in RHEL.

Version-Release number of selected component (if applicable):
tar-1.14-8.RHEL4.i386

How reproducible:
Always

Steps to Reproduce:
1. Create an Amanda backup.
2. Try to restore it: amrestore -p /dev/nst0 server /home | tar xvf - 

  

Actual Results:  Error message:
tar: ./filename: invalid sparse archive member
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers


Expected Results:  Successful restore.

Additional info:
Comment 9 Red Hat Bugzilla 2006-05-03 17:45:55 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2006-0336.html

Note You need to log in before you can comment on or make changes to this bug.