forum/How to shrink transfer repo?git-annexhttp://git-annex.branchable.com/forum/How_to_shrink_transfer_repo__63__/git-annexikiwiki2016-03-07T20:11:03Zcomment 1http://git-annex.branchable.com/forum/How_to_shrink_transfer_repo__63__/comment_1_6b110311f4c147dc315c4f610cf56afa/Horus2016-03-03T18:17:35Z2016-03-03T18:17:35Z
<p>Ok, I try to do 2) but it still fails:</p>
<pre><code>dropunused 265 (from astarte...) (unsafe)
Could only verify the existence of 0 out of 1 necessary copies
Rather than dropping this file, try using: git annex move
(Use --force to override this check, or adjust numcopies.)
failed
</code></pre>
<p>all repositories are reachable directly.</p>
comment 2http://git-annex.branchable.com/forum/How_to_shrink_transfer_repo__63__/comment_2_8e596cd606935d82bd6604f5c9c500a2/joey2016-03-07T19:13:08Z2016-03-07T17:52:21Z
<p>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.</p>
<p>But your problem is with <em>unused</em> 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.</p>
<p>To clean out those files, run: <code>git annex dropunused --from astarte --force</code></p>
<p>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: <code>git annex
move --unused --from astarte</code></p>
comment 3http://git-annex.branchable.com/forum/How_to_shrink_transfer_repo__63__/comment_3_c536a946b717e9bdcb883b58cd0336ae/Horus2016-03-07T20:11:03Z2016-03-07T20:11:03Z
Thanks, that worked!