forum/switching backendsgit-annexhttp://git-annex.branchable.com/forum/switching_backends/git-annexikiwiki2013-11-27T22:47:37Zcomment 1http://git-annex.branchable.com/forum/switching_backends/comment_1_ecf4109c1148dafde3519243ae3c5a03/edheil [wordpress.com]2013-11-27T22:47:37Z2013-01-28T03:20:38Z
<p>Just noticed this -- http://git-annex.branchable.com/bugs/git_annex_migrate_leaves_old_backend_versions_around/</p>
<p>so I don't need to worry about disk space bloat; they're all just hardlinks. That's cool. Still would be nice to know why they don't show up as "unused." But not as important.</p>
comment 2http://git-annex.branchable.com/forum/switching_backends/comment_2_21f465a18f40b95dafd307fce0de659a/joeyh.name2013-11-27T22:47:37Z2013-01-28T06:28:28Z
It won't show as unused as long as there are git refs that still refer to the file. That could be branches, or more likely you have not synced everything to the local repo yet.
comment 4http://git-annex.branchable.com/forum/switching_backends/comment_4_4c13d22c1695195e6b101bd20ef6bb42/edheil [wordpress.com]2013-11-27T22:47:37Z2013-01-28T14:30:55Z
<p>If by "synced to the local repo" you mean run a git annex sync, then yes, I have done that.</p>
<p>Here's an example of what I'm seeing:</p>
<pre><code>annex$ readlink subdir/subdir/file.txt
../../.git/annex/objects/zV/57/SHA256E-s3952--cb67d2cbadfea373ed8aa5ec434f246acccb33471a7e28a444138cc4fe8552c2.txt/SHA256E-s3952--cb67d2cbadfea373ed8aa5ec434f246acccb33471a7e28a444138cc4fe8552c2.txt
annex$ find .git/annex/objects/ -name SHA256-s3952--cb67d2cbadfea373ed8aa5ec434f246acccb33471a7e28a444138cc4fe8552c2
.git/annex/objects//1w/Q4/SHA256-s3952--cb67d2cbadfea373ed8aa5ec434f246acccb33471a7e28a444138cc4fe8552c2
.git/annex/objects//1w/Q4/SHA256-s3952--cb67d2cbadfea373ed8aa5ec434f246acccb33471a7e28a444138cc4fe8552c2/SHA256-s3952--cb67d2cbadfea373ed8aa5ec434f246acccb33471a7e28a444138cc4fe8552c2
annex$ git annex sync
commit
# On branch master
nothing to commit, working directory clean
ok
pull homeworld
ok
push homeworld
Everything up-to-date
ok
annex$ git annex unused
unused . (checking for unused data...) (checking master...) (checking sync/master...) (checking homeworld/master...) (checking toshiba/master...) (checking toshiba/synced/master...) ok
annex$ find .git/annex/objects/ -name SHA256-s3952--cb67d2cbadfea373ed8aa5ec434f246acccb33471a7e28a444138cc4fe8552c2
.git/annex/objects//1w/Q4/SHA256-s3952--cb67d2cbadfea373ed8aa5ec434f246acccb33471a7e28a444138cc4fe8552c2
.git/annex/objects//1w/Q4/SHA256-s3952--cb67d2cbadfea373ed8aa5ec434f246acccb33471a7e28a444138cc4fe8552c2/SHA256-s3952--cb67d2cbadfea373ed8aa5ec434f246acccb33471a7e28a444138cc4fe8552c2
annex$
</code></pre>
<p>As you can see, there are two remotes, "toshiba" and "homeworld". Neither of them is bare, they have checked out "master" branches. Could they be the reason that some of this data isn't "unused"? (I ask because I notice it reports that it is checking homeworld/master and toshiba/master when it does the unused check)</p>
comment 4http://git-annex.branchable.com/forum/switching_backends/comment_4_e1d4a48baac23fd3f67b20eba4eee8af/joeyh.name2013-11-27T22:47:37Z2013-02-05T19:16:48Z
If you have not yet run <code>git annex sync</code> on the remotes, then they are still referring to the old unmigrated keys, which is why <code>unused</code> will not remove them.