-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while creating backup - 'Repository' object has no attribute 'segments' #205
Comments
The issue seems to be with the filesystem - I want to create the backup on a HFS+ formatted disk. |
So, just to clarify, can you please give attic version, OS informations about where attic is running (OS X? Release?) / backing up to (locally mounted disk?). Besides the traceback, there was already a error msg before the exception happened: attic: /bin/bash: [Errno 95] Operation not supported: 'kanta.attic/index.tmp' So, precisely what operations needed were not supported? |
Note: this could be related to issue #202, similar exception there. |
Sorry for late response. |
Maybe also try attic 0.14. |
The error is just with one folder with afuse-mounted remote directories not accessible to attic. |
Interesting. Can you clarify what you mean with "not accessible to attic"? |
This is the only error I get from attic:
The permissions are
|
@shrx so when you ran attic, you were using another user/group than shrx/shrx? as a side note, the time stamp on that directory looks suspicious, like a 0 timestamp + 1h tz offset. |
Yes, I am running attic with sudo. |
sudo root? or sudo someoneelse? |
just sudo attic |
hmm, just a guessing: could the error when accessing the afuse-mounted stuff maybe be related to ACL / xattr support code (like trying to read ACLs/xattrs although they are not supported there)? @shrx could you reproduce on unmodified and slightly modified code? |
I have a backup system which involves three hosts making backups to a same repository on a central server. I am hitting this bug fairly regularly. I added some debug prints and it seems the problem is in repository.prepare_txn: it immediately sets self._active_txn to True, then tries to obtain a lock. The lock fails with: |
I have initialized attic with
and then wanted to create a backup with
How to fix this?
The text was updated successfully, but these errors were encountered: