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

comment

Browse source
This commit is contained in:
Joey Hess 2015-06-15 14:12:31 -04:00
parent 15d11fc903
commit 149f8ced6b
1 changed files with 17 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

17
doc/bugs/Corrupted_.git__47__annex__47__index_when_running_assistant/comment_4_5a26a33c34594ec6eb50bd675d68801a._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2015-06-15T18:05:38Z"
content="""
git does update the index file atomically (via `rename(2)`) but
that doesn't necessarily mean that the filesystem writes all
the data to disk before there is a problem.
That's a good point about `git gc` and the index; it does look
at the regular git index. But, `git gc` seems unlikely to cause any problem,
even if .git/annex/index pointed to a newer object that the git-annex branch
hadn't yet been updated to refer to; since `git gc` defaults to only
pruning objects that are 2 weeks old. The time that an object would
normally be in .git/annex/index without getting flushed in a commit
is normally measured in seconds to minutes.
"""]]