99a126bebb
The idea is that upon a merge of the git-annex branch, or a commit to the git-annex branch, the reposize database will be updated. So it should always accurately reflect the location log sizes, but it will often be behind the actual current sizes. Annex.reposizes will start with the value from the database, and get updated with each transfer, so it will reflect a process's best understanding of the current sizes. When there are multiple processes all transferring to the same repo, Annex.reposize will not reflect transfers made by the other processes since the current process started. So when using balanced preferred content, it may make suboptimal choices, including trying to transfer content to the repo when another process has already filled it up. But this is the same as if there are multiple processes running on ifferent machines, so is acceptable. The reposize will eventually get an accurate value reflecting changes made by other processes or in other repos. |
||
|---|---|---|
| .. | ||
| Keys | ||
| Benchmark.hs | ||
| ContentIdentifier.hs | ||
| Export.hs | ||
| Fsck.hs | ||
| Handle.hs | ||
| ImportFeed.hs | ||
| Init.hs | ||
| Keys.hs | ||
| Queue.hs | ||
| RawFilePath.hs | ||
| RepoSize.hs | ||
| Types.hs | ||
| Utility.hs | ||