duplicity 0.6.16 lists all backup sets as incomplete
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Critical
|
Unassigned | ||
duplicity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I have used duplicity since January and have done two full backups with incrementals inbetween and after the second full backup. I recently upgraded duplicity to version 0.6.16 from a slightly older version (might have been 0.6.14 or 0.6.15).
After the upgrade I ran an incremental backup again and noticed a warning that I had not seen before:
Warning, found incomplete backup sets, probably left from aborted session
The previous incremental backup had not printed the warning and it had completed successfully, AFAICT, as it printed Errors 0 as the last line of its output.
The warning alarmed me a bit, so I ran duplicity collection-status on my backup directory. It printed both backup chains, but also stated that 1) none of the sets contain any volumes and 2) there are 7161 incomplete backup sets, which it suggested should be cleaned up. Then I ran duplicity cleanup to see what duplicity thinks should be removed and compared the output with the contents of the backup directory.
It turned out that duplicity considers each and every difftar in the backup directory to be part of an incomplete backup set and therefore should be removed. This obviously doesn't sound right.
Changed in duplicity: | |
assignee: | Kenneth Loafman (kenneth-loafman) → nobody |
milestone: | none → 0.6.17 |
status: | In Progress → Fix Committed |
Changed in duplicity: | |
milestone: | 0.6.17 → none |
status: | Fix Committed → Fix Released |
Added the output of duplicity collection-status after downgrading to duplicity 0.6.15. Now there are no incomplete backup sets and all backup sets contain volumes.