From 4c797763d9090f3654640c4786105fb307fc35bd Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Thu, 25 Jul 2013 20:02:18 +0000 Subject: [PATCH 1/2] Added a comment --- ...comment_7_3cc5dae0351201522711a7caeecd60d5._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/remote_files_appear_but_are_unreadable_because_their_symlink_targets_don__39__t_exist/comment_7_3cc5dae0351201522711a7caeecd60d5._comment diff --git a/doc/bugs/remote_files_appear_but_are_unreadable_because_their_symlink_targets_don__39__t_exist/comment_7_3cc5dae0351201522711a7caeecd60d5._comment b/doc/bugs/remote_files_appear_but_are_unreadable_because_their_symlink_targets_don__39__t_exist/comment_7_3cc5dae0351201522711a7caeecd60d5._comment new file mode 100644 index 0000000000..832f38fa5d --- /dev/null +++ b/doc/bugs/remote_files_appear_but_are_unreadable_because_their_symlink_targets_don__39__t_exist/comment_7_3cc5dae0351201522711a7caeecd60d5._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="2001:4978:f:21a::2" + subject="comment 7" + date="2013-07-25T20:02:18Z" + content=""" +What settings does `.git/config` have for the git remote created by the local pairing process? + +Since I can't reproduce any problems with local pairing -- it works great on this network -- you will need to enable debugging, reproduce the bug, and send a debug log for me to debug this any further. +"""]] From 3194701c051a0add506718f030ffe74e44f8b313 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Thu, 25 Jul 2013 20:12:06 +0000 Subject: [PATCH 2/2] Added a comment --- ...mment_2_23207ecabd4b41d9551d0491fa71e96b._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/non-repos_in_repositories_list___40__+_other_weird_output__41___from_git_annex_status/comment_2_23207ecabd4b41d9551d0491fa71e96b._comment diff --git a/doc/bugs/non-repos_in_repositories_list___40__+_other_weird_output__41___from_git_annex_status/comment_2_23207ecabd4b41d9551d0491fa71e96b._comment b/doc/bugs/non-repos_in_repositories_list___40__+_other_weird_output__41___from_git_annex_status/comment_2_23207ecabd4b41d9551d0491fa71e96b._comment new file mode 100644 index 0000000000..3c9d1f36f9 --- /dev/null +++ b/doc/bugs/non-repos_in_repositories_list___40__+_other_weird_output__41___from_git_annex_status/comment_2_23207ecabd4b41d9551d0491fa71e96b._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="2001:4978:f:21a::2" + subject="comment 2" + date="2013-07-25T20:12:06Z" + content=""" +Please paste the output of: `git show git-annex:uuid.log` + +The file seems to have a lot of garbage in it. The \"merging -- 10.10.10.10__mnt_annex_00_annex/git-annex into git-annex (recovery from race)\" in particular is only ever passed to git as the commit message. It should not be possible for it to appear in a file unless data has somehow become corrupted. + +So, I think you should also run `git fsck`. You may also find that it helps to shut down any running git-annex, and move `.git/annex/index` away to a backup location. A corrupted index file would be kind of be the best scenario since git-annex can automatically rebuild it from the git repository.. +"""]]