I have a client repository with an archive/ directory. If I let the assistant sync the repos or initiate a manual git annex sync --content the contents of the archive directory is filled up.
I can't see why this happens. The repo is a client repo with the standard preferred contents and no required contents onfig.
One of the files that is wanted has 2 copies in backup repositories (one is trusted and one is reachable and semitrusted). git annex numcopies is 2 for one of these files. The repos were checked by git annex fsck and synced.
I'm not sure what to look for or how to debug this kind of situation. Any ideas?
Currently the best way to debug this kind of thing is to use git annex find with options to find files that match the preferred content expression. Once you have gotten git annex find to list the same files that are being transferred, you can then modify/cut down the options to narrow down what's going on.
The preferred content expression for a client repository is:
Translating this to command-line options:
You'll want to run that when the files are not located in the archive/ directory, and run it from the top of the repository.
Assuming that lists the files that are getting transferred, then you can split it into two commands, each of which checks one of the two parts of the expression that are ORed together:
Assuming the first of those lists the files and not the second, you can then split it further. The include=* part must be matching then, so checking two parts ORed within the second part:
Probably one of those will list the files and the other won't. Which will point fairly strongly at what's happening.
Yes, files in archive/ directories are only dropped from clients once they reach an archive. Backup repositories are not considered to be archives.
Of course, you can tweak the preferred content expressions to change this behavior.
I don't know if the arhive vs backup distinction makes sense really but I have heard of some users doing things that depend on it.