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 2021-05-10 10:37:28 -04:00
parent c09497dfad
commit 0ab9d0dfad
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
doc/bugs/Git_repos_corrupt_themselves/comment_1_c7fbc3da4404fb33a4b0babf068dc4d3._comment Normal file
View file

@ -0,0 +1,22 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2021-05-10T14:25:20Z"
content="""
git-annex does not write directly to your git repository; all writes go via
git. So it is hard to see how any corruption like this could be due to a
bug in git-annex.
What it usually is caused by is a filesystem losing data, eg because of an
unclean shutdown or a crash, or sometimes because of a disk error.
Setting the git config core.fsyncObjectFiles may help. Configuring the
filesystem to write data to disk more promptly (eg enabling journalling of
file contents) may help.
`git-annex repair --force` may be able to recover from this situation.
The "evacuate: strange closure" error does seem notable, something strange
is going on in the memory of git-annex. Presumably due to either a compiler
bug or some kind of memory problem.
"""]]