|
Re: amverify shows invalid sparse archive member errors
2005-12-01 19:36:15
--On December 1, 2005 7:12:30 PM -0500 Ed Kenny <ekenny AT efsdata DOT com>
wrote:
Hi there,
I need a little help. I've installed Amanda server with clients through a
firewall. Everything is OK except when the disklist includes the AIX
client the amverify command on the server produces hundreds of these
errors:
Known tar 1.15 ish bug....Debian tar 1.15.1-2 has a patch for it atleast,
though I thought that 1.15.1 upstream had it patched, it showed up in or
around 1.14 and persisted for quite a while. Debian Sarge's default tar
has the issue. 1.13.25 is known to me to be good,. though i thought it was
fixed in 1.15.1 as well, but maybe only in debians. Try finding an older
or newer tar package. 1.13.25ish, or go after 1.15.1, 1.14 definitely has
the bug.
/bin/gtar: ./987366/cred: invalid sparse archive member
/bin/gtar: ./987366/sigact: invalid sparse archive member
/bin/gtar: ./991470/sigact: invalid sparse archive member
/bin/gtar: ./995570/cred: invalid sparse archive member
/bin/gtar: ./995570/sigact: invalid sparse archive member
/bin/gtar: ./999676/sigact: invalid sparse archive member
The tar version from both machines:
AIX Client:
(/)-> which tar
/usr/bin/tar
(/)-> /usr/bin/tar --version
tar (GNU tar) 1.15.1
(/)->
RedHat Server:
(/root)-> which tar
/bin/tar
(/root)-> /bin/tar --version
tar (GNU tar) 1.15.1
(/root)->
amverify does not write to the /tmp/amanda place like it’s supposed to
either.
Any ideas?
--
"Genius might be described as a supreme capacity for getting its possessors
into trouble of all kinds."
-- Samuel Butler
|
|
|
