I have one idea, based on my experience yesterday. I renamed the /home/scohen/Taormina directory and then created a new directory of that name on the remote drive. A quick check of disk space informed me that I would not have enough room for a full backup on the remote drive. So I looked more closely and saw that there were a lot of very old backups under another directory that I could easily do without on the drive, and deleted those, ran the backup successfully.
My idea is this: what happens if there is not enough room to complete the backup on the intended drive? What error message does duplicity give in that case? I have no memory of any particular error message on 2021/10/07, though I do remember a problem, and being unable to solve it then, I simply gave up on backups for awhile, which I hoped to get back to with 22.04. My idea is that this situation could lead to a truncated backup file, and if the error message were not clear, confusion on the part of the user. If a backup fails due to lack of disk space on the destination, a specific error message to that effect would be useful. I don't know if that's what happened here but it could be. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1970124 Title: duplicity backup fails with obscure error message Ubuntu 22.04 Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Invalid Bug description: I try to do a backup onto a network location (ssh://192.168.1.61 - I can successfully connect to this location via ssh). The backup completes the scan phase, then dies with error messages like this: Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2: (<class 'EOFError'>, EOFError('Compressed file ended before the end- of-stream marker was reached'), <traceback object at 0x7f5f660da740>) While the backup is running, we can see a duplicity* directory under /tmp: $ ll /tmp/duplicity-i6olpr17-tempdir/ total 16 drwx------ 2 scohen scohen 4096 Apr 24 12:52 ./ drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../ -rw------- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1 However, note that this is not the directory mentioned in the failure message. A scan of the directory after the failure reveals no files like /tmp/dupl* Why is it trying to read files that do not exist? $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 $ apt-cache policy duplicity duplicity: Installed: 0.8.21-1build1 Candidate: 0.8.21-1build1 Version table: *** 0.8.21-1build1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1970124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
