summaryrefslogtreecommitdiff
path: root/doc/bugs/inAnnex_check_failed_repeatedly_for_present_content_v6/comment_4_90062420b67a7f364f5ece947408798f._comment
blob: af86bec35eba76aa1e4a422fafc911531f17806f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
[[!comment format=mdwn
 username="joey"
 subject="""comment 4"""
 date="2017-09-16T16:04:24Z"
 content="""
Right, just back up the keys/db just in case, and you need to fsck at least
any files that are not locked (to repopulate the keys/db for those), 
so safest is to fsck the whole repository..

Is it possible that you've run `git annex unlock` / `git annex lock` on
some of the affected files in the past?
"""]]