From 9cff9ff02c7ffaef9cbb87d20cd55a2595f2df7b Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 7 Mar 2016 15:13:01 -0400 Subject: [PATCH] response --- ..._8e596cd606935d82bd6604f5c9c500a2._comment | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/forum/How_to_shrink_transfer_repo__63__/comment_2_8e596cd606935d82bd6604f5c9c500a2._comment diff --git a/doc/forum/How_to_shrink_transfer_repo__63__/comment_2_8e596cd606935d82bd6604f5c9c500a2._comment b/doc/forum/How_to_shrink_transfer_repo__63__/comment_2_8e596cd606935d82bd6604f5c9c500a2._comment new file mode 100644 index 0000000000..edccafb1ec --- /dev/null +++ b/doc/forum/How_to_shrink_transfer_repo__63__/comment_2_8e596cd606935d82bd6604f5c9c500a2._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2016-03-07T17:52:21Z" + content=""" +Normally, files should be dropped from the transfer repository once they +have reached all known client repositories. The drop should be done by +the client repositories, so the transfer repo doesn't need access to the +client repos to verify that they have a copy. + +But your problem is with *unused* files that are hanging around in +the transfer repo. This can happen if a file reaches the transfer repo and +then gets deleted from a client, and so the other clients never download it. + +To clean out those files, run: `git annex dropunused --from astarte --force` + +You need to "use the force" because the unused file is only present in the +transfer repo. If you want to get rid of its content for good, that's fine. +A safer option is to move the unused file to the local repo: `git annex +move --unused --from astarte` +"""]]