From 80615ae13cce7c909104ba18afcb8c6f72ce6b0e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 16 Sep 2017 12:07:12 -0400 Subject: response for gleachkr --- .../comment_4_90062420b67a7f364f5ece947408798f._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/inAnnex_check_failed_repeatedly_for_present_content_v6/comment_4_90062420b67a7f364f5ece947408798f._comment diff --git a/doc/bugs/inAnnex_check_failed_repeatedly_for_present_content_v6/comment_4_90062420b67a7f364f5ece947408798f._comment b/doc/bugs/inAnnex_check_failed_repeatedly_for_present_content_v6/comment_4_90062420b67a7f364f5ece947408798f._comment new file mode 100644 index 000000000..af86bec35 --- /dev/null +++ b/doc/bugs/inAnnex_check_failed_repeatedly_for_present_content_v6/comment_4_90062420b67a7f364f5ece947408798f._comment @@ -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? +"""]] -- cgit v1.2.3