Activity log for bug #1022455

Date Who What changed Old value New value Message
2012-07-09 06:24:51 Eugene San bug added bug
2012-07-09 06:50:50 Eugene San description Cleanup mechanism seems to be broken, at least for my setup and in version provided with precise. Setup: Precise with 2 accounts set to backup daily with "at least a month" to local volume. Both account had backups for 3 last months. Each full set take ~1GB and incremental are ~25MB. Temp folder resides on separate volume with at least 2x more space then required for single set. Target volume had 90% / ~50GB free. Problem: After last full backup, both account left with only latest full set and volumes of set before latest, but WITHOUT signatures, making data useless! Cache (~/.cache/deja-dup) contained only signatures of latest set. Expected: Even if "low space" is triggered on 90%, which seems un logical, at least 2 recent sets should be left. Cleanup mechanism seems to be broken, at least for my setup and in version provided with precise. Setup: Precise with 2 accounts set to backup daily with "at least a month" to local volume. Both account had backups for 3 last months. Each full set take ~1GB and incremental are ~25MB. Temp folder resides on separate volume with at least 2x more space then required for single set. Target volume had 90% / ~50GB free. Problem: After last full backup, both account left with only latest full set and volumes of 1 or 2 sets before latest, but WITHOUT full-signatures, making data useless! Cache (~/.cache/deja-dup) contained only signatures of latest set. Expected: Even if "low space" is triggered on 90%, which seems un logical, at least 2 recent sets should be left.
2012-07-09 06:51:08 Eugene San bug task added deja-dup
2012-07-09 06:51:46 Eugene San bug task added duplicity
2012-07-09 08:33:08 Eugene San affects duplicity duplicity (Ubuntu)
2012-07-09 08:34:05 Eugene San bug task deleted deja-dup
2012-07-09 08:36:55 Eugene San description Cleanup mechanism seems to be broken, at least for my setup and in version provided with precise. Setup: Precise with 2 accounts set to backup daily with "at least a month" to local volume. Both account had backups for 3 last months. Each full set take ~1GB and incremental are ~25MB. Temp folder resides on separate volume with at least 2x more space then required for single set. Target volume had 90% / ~50GB free. Problem: After last full backup, both account left with only latest full set and volumes of 1 or 2 sets before latest, but WITHOUT full-signatures, making data useless! Cache (~/.cache/deja-dup) contained only signatures of latest set. Expected: Even if "low space" is triggered on 90%, which seems un logical, at least 2 recent sets should be left. Cleanup mechanism seems to be broken, at least for my setup and in version provided with precise. Setup: Precise with 2 accounts set to backup daily with "at least a month" to local volume. Both account had backups for 3 last months. Each full set take ~1GB and incremental are ~25MB. Temp folder resides on separate volume with at least 2x more space then required for single set. Target volume had 90% / ~50GB free. Problem: After last full backup, both account left with only latest full set and volumes of 1 or 2 sets before latest, but WITHOUT full-signatures and inc-signatures, making backup useless! Cache (~/.cache/deja-dup) contained only signatures of latest set. Expected: Even if "low space" was triggered on 90%, which seems to be bad idea, at least 2 working recent sets should be left. duplicity: 0.6.18-0ubuntu3 deja-dup: 22.0-0ubuntu2
2017-02-14 10:21:39 Vej tags precise