diff options
| author |  CandyAngel <CandyAngel@web> | 2017-07-21 09:25:25 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2017-07-21 09:25:25 +0000 |
| commit | 88f3f3cb3f655f0da927b9cde60bc010b109cadb (patch) | |
| tree | 9f2e58d195a7af5586ca8b62c5b31ea7889abcaa | |
| parent | 72d8ef36df0d308240989feaa06563fc52132079 (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/Rebuild_a_set_of_repos_from_checked-out_trees_and_.git__47__annex__47__objects__63__/comment_1_456772b5b0deb0c121d7feb5dcf41979._comment | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/forum/Rebuild_a_set_of_repos_from_checked-out_trees_and_.git__47__annex__47__objects__63__/comment_1_456772b5b0deb0c121d7feb5dcf41979._comment b/doc/forum/Rebuild_a_set_of_repos_from_checked-out_trees_and_.git__47__annex__47__objects__63__/comment_1_456772b5b0deb0c121d7feb5dcf41979._comment new file mode 100644 index 000000000..a6389d995 --- /dev/null +++ b/doc/forum/Rebuild_a_set_of_repos_from_checked-out_trees_and_.git__47__annex__47__objects__63__/comment_1_456772b5b0deb0c121d7feb5dcf41979._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="CandyAngel" + avatar="http://cdn.libravatar.org/avatar/15c0aade8bec5bf004f939dd73cf9ed8" + subject="comment 1" + date="2017-07-21T09:25:25Z" + content=""" +My solution is very roundabout but preserves a lot of information, but did involve buying another drive (and exclusively using v5 indirect mode!). + +I create a new repository (on the new drive) which I import all the contents of the \"keyfiles\" (contents of .git/annex/objects). Then I create another repository with the filelinks (symlinks pointing to .git/annex/objects). After adding the keyfiles remote to this, this lets me see which content is present and valid, which got corrupted, is missing etc. + +Then I can move the valid content from this recovery annex into a proper annex and try and repair/find the corrupted/missing. +"""]] |