diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-06-15 14:12:31 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-06-15 14:12:31 -0400 |
| commit | bc62e1efe9d76b860571f78b396a4a56e3121aba (patch) | |
| tree | 33fb32d42f4c2d02ccb18d6b19152d01eb9d7731 /doc | |
| parent | c518d9d592b99453cad7032aa72b228d6b90f17b (diff) | |
comment
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/bugs/Corrupted_.git__47__annex__47__index_when_running_assistant/comment_4_5a26a33c34594ec6eb50bd675d68801a._comment | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/bugs/Corrupted_.git__47__annex__47__index_when_running_assistant/comment_4_5a26a33c34594ec6eb50bd675d68801a._comment b/doc/bugs/Corrupted_.git__47__annex__47__index_when_running_assistant/comment_4_5a26a33c34594ec6eb50bd675d68801a._comment new file mode 100644 index 000000000..4b41d988d --- /dev/null +++ b/doc/bugs/Corrupted_.git__47__annex__47__index_when_running_assistant/comment_4_5a26a33c34594ec6eb50bd675d68801a._comment @@ -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. +"""]] |