From 54fe495fd4f3675dfae53af6a37f71f1d4c07272 Mon Sep 17 00:00:00 2001
From: Joey Hess <joeyh@joeyh.name>
Date: Wed, 25 Feb 2015 14:27:04 -0400
Subject: comment

---
 ...ent_1_e13d7e142e4f3c33afb1e445a1a4c093._comment | 29 ++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 doc/bugs/false_positives_from_fsck_in_bare_repo/comment_1_e13d7e142e4f3c33afb1e445a1a4c093._comment

diff --git a/doc/bugs/false_positives_from_fsck_in_bare_repo/comment_1_e13d7e142e4f3c33afb1e445a1a4c093._comment b/doc/bugs/false_positives_from_fsck_in_bare_repo/comment_1_e13d7e142e4f3c33afb1e445a1a4c093._comment
new file mode 100644
index 000000000..e369bb3d4
--- /dev/null
+++ b/doc/bugs/false_positives_from_fsck_in_bare_repo/comment_1_e13d7e142e4f3c33afb1e445a1a4c093._comment
@@ -0,0 +1,29 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-02-25T18:22:00Z"
+ content="""
+I tried to reproduce this by eg, making a bare repo that contained
+the only known copy of a file. No problem.
+
+<pre>
+joey@darkstar:~/tmp/2.git>git annex fsck
+(merging synced/git-annex into git-annex...)
+fsck
+SHA256E-s30--20c71ffd77c7f25e52416eb6afd36bf8df9410a9942d8a42e7caf74f6cfa5fb8 (checksum...)
+ok
+</pre>
+
+I then purposefully told git-annex the file was not located in the bare
+repo, even though it was there, fscked again, and it had no trouble
+fixing the location log to reflect reality:
+
+<pre>
+joey@darkstar:~/tmp/2.git>git annex fsck
+fsck SHA256E-s30--20c71ffd77c7f25e52416eb6afd36bf8df9410a9942d8a42e7caf74f6cfa5fb8 (fixing location log) (checksum...)
+ok
+(recording state in git...)
+</pre>
+
+You will need to investigate further why git-annex is not seeing the file.
+"""]]
-- 
cgit v1.2.3