When snapshot will be too large, backintime tries anyway, fails silently, leaves disk-filling "new_snapshot" behind, & subsequent backups fail silently even if not too large

Bug #861569 reported by Tom on 2011-09-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Back In Time
New
Undecided
Unassigned
backintime (Debian)
New
Undecided
Unassigned

Bug Description

I occasionally make the mistake of leaving in a backed-up directory a large temporary file/directory that cannot fit in the remaining space on the backup media.

I would have thought that backintime would see that it won't succeed before it even starts. It could then send an email or desktop notification to alert me.

Instead, backintime fills up the backup medium with a new_snapshot directory, then silently terminates without finishing the backup, alerting me of the trouble, or even removing this huge directory. The GUI will even state that the backup succeeded in its status line if it is running, though the backup will, unsurprisingly, not appear in the snapshot list.

I don't even get an email or notification the next day when backintime fails to take another shapshot. It will just keep silently failing to back up, even if the large temporary files have since been removed, until someone deletes the "new_snapshot" directory.

This is obviously terribly broken.

I am, of course, running backintime 0.9.26-4 from Debian Squeeze (stable).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers