Backup od 4.7 TB fills an 8 TB disks after 5 days

Bug #1878577 reported by Pierre-Yves Saumont on 2020-05-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Déjà Dup
Undecided
Unassigned

Bug Description

Using Ubuntu 20.4 - Deja Dup version 40.6

After an initial backup of 3.5 TB to an empty disk of 8 TB capacity (that lasted for more than 3 days), daily backups went fine for 5 days. Then, I got the following error message:

"Giving up after 5 attempts: Error splicing file, no space left in device.

No files have been removed. Only files have been added and the size of the data is now 3.8 TB. But the destination disk (8 TB) is full, containing 151 930 files with a size of 52 MB each, so the disk is full.

The problem is that Déjà Dup is supposed to only store the differences, so by only adding files to the backed up data, the size of the backup should be more or less equivalent to the size of the original data. Here, it has doubled in five days.

deja-dup.log is empty after running the command. The command may not be let running since it is backing up the whole data, which would last several days (but would fail since the disk is full)

deja-dup.settings:

org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD', '/media/pysaumont/c71a07b4-1b19-4942-8fc6-0440c4a0ac8b/.Trash-1000']
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup periodic-period 1
org.gnome.DejaDup include-list ['$HOME', '/media/pysaumont/c71a07b4-1b19-4942-8fc6-0440c4a0ac8b']
org.gnome.DejaDup prompt-check '2020-04-29T17:37:26+00'
org.gnome.DejaDup periodic true
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup last-run '2020-05-10T10:10:29+00'
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup last-backup '2020-05-10T10:10:29+00'
org.gnome.DejaDup backend 'drive'
org.gnome.DejaDup nag-check '2020-05-04T02:18:06+00'
org.gnome.DejaDup.S3 folder 'NASDCD96'
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.Rackspace container 'NASDCD96'
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack container 'NASDCD96'
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.GCS folder 'NASDCD96'
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.Local folder 'NASDCD96'
org.gnome.DejaDup.Google folder 'NASDCD96'
org.gnome.DejaDup.GOA folder '$HOSTNAME'
org.gnome.DejaDup.GOA id ''
org.gnome.DejaDup.GOA type ''
org.gnome.DejaDup.GOA migrated false
org.gnome.DejaDup.Drive folder 'NASDCD96'
org.gnome.DejaDup.Drive uuid '5BCA9F0A0E46D175'
org.gnome.DejaDup.Drive name '8,0 TB Volume'
org.gnome.DejaDup.Drive icon '. GThemedIcon drive-harddisk-usb drive-harddisk drive drive-harddisk-usb-symbolic drive-harddisk-symbolic drive-symbolic'
org.gnome.DejaDup.File path ''
org.gnome.DejaDup.File relpath @ay []
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File migrated true
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.Remote folder 'NASDCD96'
org.gnome.DejaDup.Remote uri ''

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

Other bug subscribers