← Back to team overview

duplicity-team team mailing list archive

Re: 0.6.01 picking up too many diffs; incorrectly detects 0 volume increment

 

> What this means is that you really did not get far enough for a restart.

Ok - I hit ctrl-c pretty early.

>  I guess the message should be clearer.  The manifest is written, but
> the sigtar file has not really made it yet.  In this one case there's
> nothing to be done, but in cases where the count is something like
> manifest has 4 and the remote has 3, the manifest can be corrected.

Roger. In fact though, re-running *again* I am again able to finally
reproduce the key error issue I think I've talked about:

Using temporary directory /tmp/duplicity-VcIec0-tempdir
Temp has 261370937344 available, backup will use approx 2411724.
Local and Remote metadata are synchronized, no sync needed.
Added incremental Backupset (start_time: Sat Jul  4 18:25:38 2009 / end_time: Sat Jul  4 18:26:00 2009)
Added incremental Backupset (start_time: Sat Jul  4 18:26:00 2009 / end_time: Tue Jul  7 18:41:17 2009)
Added incremental Backupset (start_time: Tue Jul  7 18:41:17 2009 / end_time: Tue Jul  7 18:41:31 2009)
Added incremental Backupset (start_time: Tue Jul  7 18:41:31 2009 / end_time: Tue Jul  7 20:18:54 2009)
Warning, found an unnecessary signature chain
duplicity-full-signatures.20090704T162538Z.sigtar.gpg
Warning, found incomplete backup sets, probably left from aborted session
Last inc backup left a partial set, restarting.
Last full backup date: Sat Jul  4 18:25:38 2009
Traceback (most recent call last):
  File "./duplicity-bin", line 1197, in <module>
    with_tempdir(main)
  File "./duplicity-bin", line 1190, in with_tempdir
    fn()
  File "./duplicity-bin", line 1172, in main
    incremental_backup(sig_chain)
  File "./duplicity-bin", line 484, in incremental_backup
    globals.backend)
  File "./duplicity-bin", line 252, in write_multivol
    globals.restart.setLastSaved(mf)
  File "./duplicity-bin", line 1065, in setLastSaved
    vi = mf.volume_info_dict[self.start_vol]
KeyError: 0

Though last tim e the key was 1 rather than 0. It sounds related. I'll
try to check into it tonight unless you happen to know off hand what's
going on.

Btw, what's your take on providing an explicit option to make
duplicity forget any checkpoint/restore state?

-- 
/ Peter Schuller

PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller@xxxxxxxxxxxx>'
Key retrieval: Send an E-Mail to getpgpkey@xxxxxxxxx
E-Mail: peter.schuller@xxxxxxxxxxxx Web: http://www.scode.org

Attachment: pgp4m_Myxb42s.pgp
Description: PGP signature


Follow ups

References