Restore to external disk fills root filesystem
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Duplicity |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Hello! I had a user of Deja Dup report the following behavior:
"""
I am using Ubuntu 10.10 with the Gnome desktop and am trying to perform a restore of an 80GB folder to an external disk using DejaDup 16.1.1. What happens is that at some point through the restore, the alert "Filesystem root has only ... MB of disk space remaining" pops up; a quick check at this point with the "df" command shows the root filesystem steadily filling up until it reaches full saturation, at which point the restore fails. Nothing gets actually transferred to the external disk (or nothing is reported).
...
What I figured out it does, it first restores the first file which is about 18GB in size and just about fits in the available space on the root filesystem (30GB-11GB = 19 GB). Then it starts pushing it out to the external disk and this gets restored OK. Then it starts to restore the bigger file (60GB) and at that point it fails because it has no more space in the root filesystem (it does not garbage collect the first file after having restored it to the external disk).
But of course, this is not what was happening before, when the restore used to work, because with a 60GB file to restore it could never have had enough space to cache 60GB within the 30GB of the root filesystem. Just what has changed, I do not know.
"""
The original report is here: https:/
Looks like duplicity wasn't cleaning up the temporary files?
| RVBER BACCHVS (ruberbacchus) wrote | #1 |
| Stephen Rees-Carter (valorin) wrote | #2 |
| edso (ed.so) wrote | #3 |
| Changed in duplicity: | |
| status: | New → Confirmed |
The thing which preoccupies me, which I mentioned previously, is why it used to work fine and suddenly it stopped working even though the same procedures, same size and number files were up for restore, from the same backups.
I suspect it's not simply duplicity (pardon the pun), but its actual interaction with Ubuntu that has changed something. More to the point, I suspect that one of the updates in the Ubuntu OS has broken something.
My second suspect is the mounting options for the external backup disk. Ubuntu seems to have the unfortunate tendency to vary the way it mounts the peripherals, sometimes with root ownership and sometimes not, and the mountpoints and/or device names also seem to vary from one session to another (utterly baffling to me).
So I attempted to stabilise things by defining my own mount options in /etc/fstab and retried the restoration with various such options, however without luck.
I remind of this similar bug here:
http://