TW
the problem is caused by a non-ascii access control list (maybe a user or group name with non-ascii chars).
There is no attic option to switch that off. You'ld have to edit attic/platform.py so it runs into the "else" case there.
@anarcat this is not the filename, but likely some non-ascii user or group name inside the acl.
answering your first question: They are neither incremental nor differential, it's a different method. Every backup appears to be complete, but shares counted references to common chunks with other backups....
@AbbyNormal, deduplicating backup programs’ approach is different from the older full/incremental (or differential) approach. Each backup you create with attic (or borgbackup) is a full backup that references all data...
this seems to be a bit out of scope for attic maybe, but maybe you could just use a 3rd party addition like this one: https://torsion.org/atticmatic/
To clarify (as it is not visible from the 2 tracebacks): The operation that fails in both cases is: ``` os.rename(os.path.join(self.path, 'txn.active'), os.path.join(self.path, 'txn.tmp')) ```
@Ernest0x about too much traffic / serverside prune: rather create a separate ticket about that.
I suspect this issue is caused by an internal inconsistency about whether a transaction is active or not. The code in question changed after 0.13, so it might be that...
This is because the RepoCache which is used for remote repos can only cache 2GB. I've fixed that in my repo.