Misleading log messages when running remove-all-inc-of-but-n-full

Bug #1448094 reported by Tomáš Zvala on 2015-04-24
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
Medium
Unassigned

Bug Description

When running remove-all-inc-of-but-n-full 4 I get these messages logged on every run:

Deleting backup chains at times:
Mon Dec 1 05:17:17 2014
Mon Dec 15 05:19:23 2014
Wed Dec 31 05:21:33 2014
Thu Jan 1 05:21:26 2015
Thu Jan 15 05:22:33 2015
Sat Jan 31 05:27:57 2015
Sun Feb 1 05:26:20 2015
Sun Feb 15 05:26:26 2015
Deleting incremental signature chain Sun Feb 15 05:26:26 2015
Deleting incremental signature chain Sun Feb 15 05:26:26 2015
Deleting incremental signature chain Sun Feb 1 05:26:20 2015
Deleting incremental signature chain Sun Feb 1 05:26:20 2015
Deleting incremental signature chain Sat Jan 31 05:27:57 2015
Deleting incremental signature chain Sat Jan 31 05:27:57 2015
Deleting incremental signature chain Thu Jan 15 05:22:33 2015
Deleting incremental signature chain Thu Jan 15 05:22:33 2015
Deleting incremental signature chain Thu Jan 1 05:21:26 2015
Deleting incremental signature chain Thu Jan 1 05:21:26 2015
Deleting incremental signature chain Wed Dec 31 05:21:33 2014
Deleting incremental signature chain Wed Dec 31 05:21:33 2014
Deleting incremental signature chain Mon Dec 15 05:19:23 2014
Deleting incremental signature chain Mon Dec 15 05:19:23 2014
Deleting incremental signature chain Mon Dec 1 05:17:17 2014
Deleting incremental signature chain Mon Dec 1 05:17:17 2014
Deleting incremental backup chain Sun Feb 15 05:26:26 2015
Deleting incremental backup chain Sun Feb 1 05:26:20 2015
Deleting incremental backup chain Sat Jan 31 05:27:57 2015
Deleting incremental backup chain Thu Jan 15 05:22:33 2015
Deleting incremental backup chain Thu Jan 1 05:21:26 2015
Deleting incremental backup chain Wed Dec 31 05:21:33 2014
Deleting incremental backup chain Mon Dec 15 05:19:23 2014
Deleting incremental backup chain Mon Dec 1 05:17:17 2014

Which made me think there are chains which should be deleted, but are still in the storage.

After some digging through the code I finally realized that even though duplicity says it will delete, there is nothing to be deleted, as all these are actually full backups and all the incrementals in those have been already deleted.

I seem not to be the fist one to run into this: http://comments.gmane.org/gmane.comp.sysutils.backup.duplicity.general/6214

If it made any difference, I'm running Ubuntu 14.04 and duplicity 0.7.02 from the ppa.
duplicity 0.7.02 ($reldate)
Args: /usr/bin/duplicity --s3-use-new-style -v 9 --archive-dir=/some/local/path remove-all-inc-of-but-n-full 4 --force s3+http://mybackupbucket/somebucketpath
Linux frenzy.cp.casa 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64
/usr/bin/python 2.7.6 (default, Mar 22 2014, 22:59:56)
[GCC 4.8.2]

I would really like to get less text output for backups, so I looked at this. Here is a patch against 0.7.14 fixing this.

BTW this would look nicer if both classes were more similar: Adding is_empty() to both or rename incset_list to inclist

Changed in duplicity:
status: New → Fix Released
milestone: none → 0.7.15
Changed in duplicity:
status: Fix Released → Fix Committed
importance: Undecided → Medium
Changed in duplicity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers