response for gleachkr
This commit is contained in:
parent
63dfd6cde2
commit
b7dafb4f66
1 changed files with 12 additions and 0 deletions
|
@ -0,0 +1,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?
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue