From 06ef5dacdc0b50f01ee159ac475d6a974f8229ee Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 21 Jun 2021 13:13:28 -0400 Subject: [PATCH] remove comment I made to the wrong place I am not sure what forum thread I was intending to comment on --- ..._2a9e8c859e722a334947bc9b11265c6c._comment | 23 ------------------- 1 file changed, 23 deletions(-) delete mode 100644 doc/forum/comment_1_2a9e8c859e722a334947bc9b11265c6c._comment diff --git a/doc/forum/comment_1_2a9e8c859e722a334947bc9b11265c6c._comment b/doc/forum/comment_1_2a9e8c859e722a334947bc9b11265c6c._comment deleted file mode 100644 index 11ebb5d7aa..0000000000 --- a/doc/forum/comment_1_2a9e8c859e722a334947bc9b11265c6c._comment +++ /dev/null @@ -1,23 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2021-01-04T20:31:58Z" - content=""" -There's not currently anything to automate this. I sometimes do it -manually, eg noticing that drive A is nearly full and `git-annex move --to -B` of some of its files to free up space. - -That's generally when I need space on drive A for some other purpose -than that git-annex repo. If drive A is only being used for the one -git-annex repo, then it doesn't much matter if it fills up before drive B? -So maybe setting annex.diskreserve to some sufficiently large size in that -repo on the drive would be better, so there's always space reserved for the -other things the drive is being used for. - -[[design/balanced_preferred_content]] is an old attempt at designing -a way to automate balancing between drives. Never quite got implemented, -because of the limitations documented in it. -It might be that it would work well enough for some use cases? - -I'd welcome thoughts on this topic. -"""]]