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

Added a comment

Browse source
This commit is contained in:
zardoz 2014-09-07 14:04:51 +00:00 • committed by admin
parent 0b898aee18
commit ab1ab57f80
1 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

22
doc/bugs/__34__error:_invalid_object__34____44___after_add__59___cannot_commit/comment_9_7c98c8b291fdf28a09ccb6c7e4001d5a._comment Normal file
View file

@ -0,0 +1,22 @@
[[!comment format=mdwn
username="zardoz"
ip="78.48.163.229"
subject="comment 9"
date="2014-09-07T14:04:51Z"
content="""
Any ideas? I noticed one alternative way (cf. the reset workaround
above) to make «git annex add» work again is by deleting
.git/annex/index*. Is this safe?
In both repos, I had not even staged annex additions before the index
was corrupted; the corruption must somehow have been left-over from
earlier actions, altough all previous additions succeeded at the time,
before both repositories mysteriously stopped working (in the context
of backend-migration).
I still have the original snapshots around if you’d like to debug
this. As noted, «git fsck» succeeds, and all the block-level checksums
check out, so the problem can’t be on the block device or file-system
level.
"""]]