From 852e6d91b3bf031647f91a979826857f6d223dba Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawksMCAJI5ZUb1LaKL9nxVzEOTsfNkXI7WU" Date: Mon, 13 Apr 2015 06:18:47 +0000 Subject: [PATCH] --- doc/bugs/fsck_reports_unsolvable_problem.mdwn | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/bugs/fsck_reports_unsolvable_problem.mdwn diff --git a/doc/bugs/fsck_reports_unsolvable_problem.mdwn b/doc/bugs/fsck_reports_unsolvable_problem.mdwn new file mode 100644 index 0000000000..660bb1968c --- /dev/null +++ b/doc/bugs/fsck_reports_unsolvable_problem.mdwn @@ -0,0 +1,18 @@ +### Please describe the problem. + +On my bare git-annex repo, `git annex fsck -q` reports: + + ** No known copies exist of SHA256E-s1212237--d2edd369f6a9005e23f022c7d797b166c66b90defc561329dbafab9a0fc0c7fc.jpg + +`git log -SSA256E...` returns nothing. `git annex repair` and `git annex forget` do not fix the problem. + +This means that running `fsck` from cron or a script will now always fail. There should be a way to recover from this situation. + +### What steps will reproduce the problem? + +According to IRC this "can happen if you annexed a file and then deleted it without ever committing to git". + + +### What version of git-annex are you using? On what operating system? + +5.20140717 from Ubuntu utopic