deja-dup fails with "no space left" with no relevant settings to solve problem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Déjà Dup |
New
|
Undecided
|
Unassigned |
Bug Description
I'm backing up to a huge remote disk.
Backups are failing, after a lot of CPU and I/O time, with a simple "Backup Failed. No space left." message.
The lack of space appears to be the limit of about 5 GB free on /tmp, *not* to do with any limit on the target disk.
The problem is that there is no option in the interface to set what should be used for temporary space. Can I just use the same remote disk as the target? Can I avoid needing any tmp space (why do I?). I can think of various relevant fixes and improved features (eg for deja-dup to be smarter or more communicative), but the bug is that even though I've a reasonable amount of space in my /tmp, my backups are FAILING and I'm without a backup for over a week.
lsb_release -d
Description: Ubuntu 12.04 LTS
dpkg-query -W deja-dup duplicity
deja-dup 22.0-0ubuntu2
duplicity 0.6.18-0ubuntu3
org.gnome.DejaDup backend 'file'
org.gnome.DejaDup delete-after 56
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup include-list ['/home/
org.gnome.DejaDup last-backup '2012-07-
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup last-run '2012-07-
org.gnome.DejaDup periodic true
org.gnome.DejaDup periodic-period 1
org.gnome.DejaDup prompt-check 'disabled'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup welcomed true
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
Same issue for me with a small difference, using tmpfs which has additional size restrictions depending on the amount of free memory at the time.
Is there a way to force the application to use a different location to '/tmp'?