TW
Hmm, does this happen with other dotfiles also?
Can you write a minimal script that reproduces this? - establish the minimal directory, file and mount structure - attic init / create - attic mount - ls the file...
@tobiaslangner borg dev @enkore could find / fix it (in borg, but you could use same patch for attic I guess), see the link to the closed issue right above...
attic starts the recursive walk of the filesystem at the given path. it stores the full absolute path of the files, but it does not collect metadata of the directories...
why do you refer to locking? the original post had nothing about it.
@gullevek can you still reproduce this with a current attic version? A problem is that the traceback does not contain enough information about the AttributeError that happened on the remote...
@mgrachten AFAIK this is not the case.
@erikhydro have a look at borgbackup (which is a fork of attic), a lot of issues are fixed there. iirc it is available from the backports repo. there is also...
If you don't have working posix locks (due to using a filesystem that does not correctly support them), you are out of luck with attic. I assumed you have client/server...
I use to assemble all useful filesystems under /rootfs using "mount --bind /real /rootfs/real" before backing up (so that I can get rid of /sys /dev /proc vfs and even...