diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-04-14 15:35:15 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-04-14 15:35:15 -0400 |
| commit | 513b3a639796b06828570b6da6b049095abd5b83 (patch) | |
| tree | adc204e55854d1d5d4f75689ea17fa9624142872 /doc/bugs/fsck_reports_unsolvable_problem.mdwn | |
| parent | cd4304b64943ba55ffc8beac47796affc5405fd8 (diff) | |
| parent | 1029cba6ac006b34053f3f96cbee9ecafe8cc1ae (diff) | |
Merge branch 'master' into concurrentprogress
Conflicts:
debian/changelog
Diffstat (limited to 'doc/bugs/fsck_reports_unsolvable_problem.mdwn')
| -rw-r--r-- | doc/bugs/fsck_reports_unsolvable_problem.mdwn | 20 |
1 files changed, 20 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..d0164f8bc --- /dev/null +++ b/doc/bugs/fsck_reports_unsolvable_problem.mdwn @@ -0,0 +1,20 @@ +### 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 + +[[!tag confirmed]] |