duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] Error "Bad tarinfo name ././@LongLink"


From: Rob Browning
Subject: Re: [Duplicity-talk] Error "Bad tarinfo name ././@LongLink"
Date: Sun, 09 Mar 2003 17:00:19 -0600
User-agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-pc-linux-gnu)

Ben Escoto <address@hidden> writes:

> The problem seems to be that duplicity is making a bad signature file.
> If this is true, and it happens whenever you make an incremental
> backup, then the problem must be in the initial signatures.

FWIW, it's not a big deal, but I've noticed that duplicity uses
filenames that seem to be incompatible with bash and "tar xzf".

  # tar tzf duplicity-full.2003-03-09T11\:46\:36-05\:00.vol1.difftar.gz 
  rsh: duplicity-full.2003-03-09T11: Name or service not known
  tar (child): duplicity-full.2003-03-09T11\:46\:36-05\:00.vol1.difftar.gz: 
Cannot open: Input/output error
  tar (child): Error is not recoverable: exiting now

  gzip: stdin: unexpected end of file
  tar: Child returned status 2
  tar: Error exit delayed from previous errors

I suspect it's the colons in the name causing the trouble...

> The above output is what tar should say.  All of the files should
> either start with "snapshot/" or "signature/".  If one of them says
> "././@LongLink" or something then we know the problem is with the
> signatures.

Hmm.  That doesn't seem to be the problem.  I can verify that the
contents look "right" (according to the above criteria) and then, to
check for sure:

  # zcat 'duplicity-full-signatures.2003-03-09T11:46:36-05:00.sigtar.gz' \
      | tar tf - | pcregrep -v '^signature/' | pcregrep -v '^snapshot/'
  #

In case it might matter, I'm using --no-encryption and
--null-separator for the runs.

> Another strategy would be to try to narrow the error down so it can
> be reproduced in just a few files.  Then you could send me the files
> and the command, and get me to fix it.

Right, though I'll probably need to add some annotations to the source
so I can see roughly where it is when it fails, so I'll know which
files are likely culprits.

Thanks

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4




reply via email to

[Prev in Thread] Current Thread [Next in Thread]