forum/rebuild location log from encrypted remotegit-annexhttp://git-annex.branchable.com/forum/rebuild_location_log_from_encrypted_remote/git-annexikiwiki2013-12-02T20:03:28Zcomment 1http://git-annex.branchable.com/forum/rebuild_location_log_from_encrypted_remote/comment_1_f84f955fed7b96ae6208b6ff2ec650cd/joeyh.name2013-12-01T19:59:16Z2013-12-01T19:59:16Z
<p>I think you should try to run <code>git annex copy --from needle</code>, which will be able to get the files if needle has them, even if the location log is busted.</p>
<p>(Sometimes people complain that <code>git annex copy</code> goes and checks a remote, which can be unncessarily slow, rather than just trusting the location log ... but this is why it does it!)</p>
<p>From what I can tell, the fsck downloads some file from the remote, but the download is not entirely successful. One possibility is that it downloads a file, but the file fails to be decrypted, either because you don't have the right encyption key, or because the encrypted file has actually gotten corrupted on the remote. It might be that the same problem will affect <code>git annex copy --from needle</code>, but if so it should be more clear what's happening.</p>
comment 2http://git-annex.branchable.com/forum/rebuild_location_log_from_encrypted_remote/comment_2_c0b2ce3bc7cd55a0c77ddc31493068c2/Vincent2013-12-02T01:28:19Z2013-12-02T01:28:18Z
<p>Thanks a lot for the quick response! Unfortunately, copy is just silent and does not copy the files over.</p>
<p>I don't want to waste more of your time on this. I just wish I had kept better track of the steps I took to get myself into this mess...</p>
comment 3http://git-annex.branchable.com/forum/rebuild_location_log_from_encrypted_remote/comment_3_06a73ca3dc73399ff000b642cca72de7/joeyh.name2013-12-02T20:03:28Z2013-12-02T19:53:11Z
<p>Hmm, it seems I was wrong about copy --from not checking the location log. It does.. Probably to avoid large copies trying to copy a lot of files that are not present in a remote.</p>
<p>I have now made <code>git annex copy --force --from remote</code> do what I said it would do, and that should work in your situation, I think.</p>