Comment 13 for bug 1776030

Revision history for this message
Barry Martin (barry-martin-3-c) wrote :

Update on what I found....

The easiest and fastest way to ‘correct’ is to create a new directory to back up to and change the storage location to the new back up point. I looked at permissions as suggested in one of the posts above:

barry@NZXT:~$ getfacl /media/NSA320_Backups/DejaDup_NZXT_02
getfacl: Removing leading '/' from absolute path names
# file: media/NSA320_Backups/DejaDup_NZXT_02
# owner: barry
# group: barry
user::rwx
group::rwx
other::rwx

barry@NZXT:~$ ls -lS /media/NSA320_Backups
total 0
drwxrwxrwx 2 barry barry 0 Apr 29 2020 Backend_3
drwxrwxrwx 2 barry barry 0 Oct 25 19:24 DejaDup_NZXT_01
drwxrwxrwx 2 barry barry 0 Dec 17 02:36 DejaDup_NZXT_02

barry@NZXT:~$ ls -lS /media/NSA320_Backups/DejaDup_NZXT_02
<snip>
-rwxrwxrwx 1 barry barry 187 Jul 30 03:33 duplicity-inc.20210729T082208Z.to.20210730T082213Z.manifest
-rwxrwxrwx 1 barry barry 187 Aug 10 03:33 duplicity-inc.20210809T082232Z.to.20210810T082229Z.manifest

To me looks like everyone and their uncle can do what they want (so chmod 777?). No idea. LIS, I created and pointed to a new directory and it’s making a full backup now.