From 064fdf531f6acdc3fda0339705ce92927b70e41a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 24 Jun 2025 12:24:45 -0400 Subject: [PATCH] comment --- ..._6f128a1a28298bb5662fa32e9b350946._comment | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/forum/Fill_remotes_sequentially/comment_6_6f128a1a28298bb5662fa32e9b350946._comment diff --git a/doc/forum/Fill_remotes_sequentially/comment_6_6f128a1a28298bb5662fa32e9b350946._comment b/doc/forum/Fill_remotes_sequentially/comment_6_6f128a1a28298bb5662fa32e9b350946._comment new file mode 100644 index 0000000000..b73f832b44 --- /dev/null +++ b/doc/forum/Fill_remotes_sequentially/comment_6_6f128a1a28298bb5662fa32e9b350946._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 6""" + date="2025-06-24T16:13:56Z" + content=""" +> It seems like that the remote's cost could be a way to define the order in which the remotes are filled? + +Yes because git-annex always tries to use the lowest cost remote first when +storing or retrieving a file. So using eg the standard archive group +preferred content setting, it would store a file on the lowest cost remote, +and then the other remotes would no longer want a copy of the file since it +was already stored to one. + +`GETCOST` defines the default cost for a special remote. So rather than +configuring `remote..annex-cost-command`, your special remote could +check if the expected tape is currently in the drive, and return a lower cost. + +If the cost needs to change while git-annex is running, due eg to a tape +being swapped, it could re-query `GETCOST` after every file. Which would +be less expensive than running a cost command. I think that a config +setting to make it do that is a feasible change to make to git-annex. + +(Ignore `GETAVAILABILITY`, it's barely used and only by the assistant.) +"""]]