Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 171625

Summary: "invalid sparse archive member" when extracting tars
Product: Red Hat Enterprise Linux 4 Reporter: Josh Kelley <joshkel>
Component: tarAssignee: Peter Vrabec <pvrabec>
Status: CLOSED ERRATA QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: RHEL4U3NAK
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: ---
Bug Depends On:    
Bug Blocks: 187538    

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