From 173500872ff91af19fa1c0c4514423ef9687fc3a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 22 Aug 2024 07:17:04 -0400 Subject: [PATCH] update --- doc/todo/git-annex_proxies.mdwn | 18 ------------------ 1 file changed, 18 deletions(-) diff --git a/doc/todo/git-annex_proxies.mdwn b/doc/todo/git-annex_proxies.mdwn index f8606e5aba..ebdcae3433 100644 --- a/doc/todo/git-annex_proxies.mdwn +++ b/doc/todo/git-annex_proxies.mdwn @@ -69,24 +69,6 @@ Planned schedule of work: command behave non-ideally, the same as the thread concurrency problems. -* implement size-based balancing, so all balanced repositories are around - the same percent full, perhaps as another preferred - content expression. - -* `fullybalanced=foo:2` can get stuck in suboptimal situations. Eg, - when 2 out of 3 repositories are full, and the 3rd is mostly empty, - it is no longer possible to add new files to 2 repositories. - Moving some files from one of the full repositories to the empty one - would improve things, but is there any way for fullybalanced to know - when it makes sense to do that? - - If this is not resolved, it may be better to lose the ":number" part - of balanced and fullybalanced. With 1 copy balanced, this situation does - not occur. Users wanting 2 copies can have 2 groups which are each - balanced, although that would mean more repositories on more drives. - - Size based rebalancing may offer a solution; see design. - * `git-annex info` in the limitedcalc path in cachedAllRepoData double-counts redundant information from the journal due to using overLocationLogs. In the other path it does not, and this should be fixed