From a5b250cd2aeb899c387d5a314be27b29406aadd5 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Thu, 15 May 2014 20:22:41 +0000 Subject: [PATCH] Added a comment --- ...1_d370b044da3bfebf9e4c90ce1e243587._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/forum/error:_refs__47__heads__47__git-annex_does_not_point_to_a_valid_object__33__/comment_1_d370b044da3bfebf9e4c90ce1e243587._comment diff --git a/doc/forum/error:_refs__47__heads__47__git-annex_does_not_point_to_a_valid_object__33__/comment_1_d370b044da3bfebf9e4c90ce1e243587._comment b/doc/forum/error:_refs__47__heads__47__git-annex_does_not_point_to_a_valid_object__33__/comment_1_d370b044da3bfebf9e4c90ce1e243587._comment new file mode 100644 index 0000000000..cf7601d408 --- /dev/null +++ b/doc/forum/error:_refs__47__heads__47__git-annex_does_not_point_to_a_valid_object__33__/comment_1_d370b044da3bfebf9e4c90ce1e243587._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 1" + date="2014-05-15T20:22:40Z" + content=""" +This means that a git commit's data has gotten lost somehow. You can verify that by trying + + git show 993859515190743e9bed7fc8e697d5ac4e2d03a0 + +The most common reason for this to happen is if the system is shutdown unexpectedly while git-annex is running. Or, if this repository is on a removable drive, if it got removed before the data could be written. + +You can probably fix the problem by running: + + git annex repair + +(Code formatting: Use 4 spaces.) +"""]]