[Top][All Lists]

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

Re: [Duplicity-talk] Why do I have a 19GB ~/.cache/duplicity folder?

From: Kenneth Loafman
Subject: Re: [Duplicity-talk] Why do I have a 19GB ~/.cache/duplicity folder?
Date: Sat, 06 Mar 2010 05:54:42 -0600
User-agent: Thunderbird (X11/20090817)

Tim Riemenschneider wrote:
> Kenneth Loafman schrieb:
>> The OP never did file a bug report and its not been "fixed".
> The OP didn't, but I did ;-)
> The bugid is https://bugs.launchpad.net/duplicity/+bug/519948

Sorry, I missed that when I looked.

>> The large size is in the nature of the beast that is incremental backup.
>>  We try to keep backup sizes small, so we use small chunks for signature
>> comparison.  This produces more signatures on large files, and a minimal
>> backup.  Larger chunks would produce smaller signatures and a smaller
>> backup, so the only "fix" is to allow the user to select signature size
>> thresholds on their own.
>> I've not had much time to chase this, but the code that determines the
>> chunk size is simple, so it may not take much to make the change.
> As I said in my earlier post, that could be a problem of signatures of
> old backups still lying around (at least that was the case with one of
> my backups. After manually deleting older signatures (those, where no
> difftars where around anymore) on the backend, the size of my
> .cache-directory was reduced from 3 GB to 1 GB.

'duplicity cleanup' may be the culprit in this one.  I'll check that.

>> Plus, my suspicion is that these large metadata stores are a direct
>> result of long strings of incremental backups with no full backup at
>> regular intervals.  Since this is bad practice in general, I've not
>> really been inclined to fix duplicity to encourage it.
> When that is the case (with the OP), then you are right, that should not
> be encouraged. But if it's old, unused signatures lying around, then the
> size gets even bigger if you do full-backups more often!
> (Ok, in the meantime I found the --extra-cleanup option, which deposed
> of all the old signatures. But that is not the default)

The extra-cleanup may have worked, but cleanup by itself should have
removed any old sigtars that were not associated with a current backup.


Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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