diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawksMCAJI5ZUb1LaKL9nxVzEOTsfNkXI7WU <Felix@web> | 2015-04-13 06:18:47 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-04-13 06:18:47 +0000 |
| commit | 320425b219c5e2131927ac3d0a8118f690396502 (patch) | |
| tree | 8952be322264452e9fbb0ea8de38cb1e4909c40a | |
| parent | af179125761de007d2b6429d6c55ee4e1da62771 (diff) | |
| -rw-r--r-- | doc/bugs/fsck_reports_unsolvable_problem.mdwn | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/bugs/fsck_reports_unsolvable_problem.mdwn b/doc/bugs/fsck_reports_unsolvable_problem.mdwn new file mode 100644 index 000000000..660bb1968 --- /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 |