restic: Exclude file is being ignored
After updating from restic 0.8.1 to 0.8.3 (with no other changes to my setup) restic has started throwing a permissions error on a path that is listed in an exclude file, so should be getting ignored.
Output of restic version
restic 0.8.3
compiled with go1.10 on linux/amd64
How did you run restic exactly?
restic-0.8.3 backup --exclude-file /path/to/exclude --no-cache -r gs:bucket:/restic /mnt/project
using parent snapshot e3f71c8b
scan [/mnt/project]
error for /mnt/project/.glusterfs: open /mnt/project/.glusterfs: permission denied
...
The exclude file contains:
.glusterfs
.glusterfs/*
.migrated
.migrated/*
.trashcan
.trashcan/*
css/*
ctools/*
js/*
styles/*
temp/*
tmp/*
xmlsitemap/*
What backend/server/service did you use to store the repository?
Google Cloud
Expected behavior
I want restic to not try to access the paths listed in the exclude file.
Actual behavior
Restic tries to access files and directories under paths listed in the exclude file.
Steps to reproduce the behavior
Do you have any idea what may have caused this?
I updated from restic 0.8.1 to 0.8.3.
0.8.1 did not throw the permissions error on the .glusterfs directory when running backups and restoring a snapshot made with 0.8.1 does not restore a .glusterfs dir (or any of the other paths listed in the exclude file), so it was happy with my exclude file syntax.
Do you have an idea how to solve the issue?
Other than downgrade to 0.8.1, sorry, no.
Did restic help you or made you happy in any way?
Restic makes me happy, but not nearly as happy as the helpfulness and responsiveness of the developer 😃
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 15 (7 by maintainers)
Cool, thanks for the confirmation, I’m closing this issue.
I bumped my install to 0.9.1 last week and the warning has indeed gone away - thank you 😃
So, in summary: This issue is caused by restic trying to
stata directory before checking if it would be excluded. It’s hard to change that with the way the code is structured right now. I’ll try to get this one done after #1494 is finished. 😃Ah, I only now saw your comment here. I think you’re right, it’s the same issue. I did not recognize the underlying cause before, thank you!