mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

back from the dead, or not

Browse source
This commit is contained in:
https://id.koumbit.net/anarcat 2014-07-28 22:40:43 +00:00 • committed by admin
parent 68189cc519
commit 3a5da63dc3
1 changed files with 23 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

23
doc/bugs/direct_command_leaves_repository_inconsistent_if_interrupted.mdwn Normal file
View file

@ -0,0 +1,23 @@
### Please describe the problem.
When `git annex direct` is interrupted (either through a power outage or deliberate `control-c`) it may leave the repository in an inconsistent state.
A typical situation is `git-annex` believing that the repo is in `indirect` mode while the files are not symlinks anymore.
I believe I have described this problem here before, but the bug report was deleted as part of the may 29th purge (222f78e9eadd3d2cc40ec94ab22241823a7d50d9), file `doc/bugs/git_annex_indirect_can_fail_catastrophically.mdwn`.
### What steps will reproduce the problem?
`git annex direct` on a large repository, `control-c` before it finishes.
Observe how a lot of files are now considered to be in the famous [[typechange status|forum/git-status_typechange_in_direct_mode/]] in git.
### What version of git-annex are you using? On what operating system?
5.20140717 on Debian Jessie.
### Please provide any additional information below.
I wish i could resume the `git annex direct` command, but this will do a `git commit -a` and therefore commit all those files to git directly. It still seems to me that `git annex` should never run `git commit -a` for exactly that kind of situations.
I think that's it for now. -- [[anarcat]]