From 7ece9b4fed44445d88ca6405eeeb61214406ab21 Mon Sep 17 00:00:00 2001 From: "gleachkr@7c488e398809299a1100b93f8884de43dee83674" Date: Sat, 16 Sep 2017 16:46:48 +0000 Subject: Added a comment: Thanks! --- .../comment_6_fce1ef0377e00fb9431d4c8b0215387b._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/bugs/inAnnex_check_failed_repeatedly_for_present_content_v6/comment_6_fce1ef0377e00fb9431d4c8b0215387b._comment diff --git a/doc/bugs/inAnnex_check_failed_repeatedly_for_present_content_v6/comment_6_fce1ef0377e00fb9431d4c8b0215387b._comment b/doc/bugs/inAnnex_check_failed_repeatedly_for_present_content_v6/comment_6_fce1ef0377e00fb9431d4c8b0215387b._comment new file mode 100644 index 000000000..5cd5cbf45 --- /dev/null +++ b/doc/bugs/inAnnex_check_failed_repeatedly_for_present_content_v6/comment_6_fce1ef0377e00fb9431d4c8b0215387b._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="gleachkr@7c488e398809299a1100b93f8884de43dee83674" + nickname="gleachkr" + avatar="http://cdn.libravatar.org/avatar/c7ce6b5eae91547b25e9a05fc7c8cf22" + subject="Thanks!" + date="2017-09-16T16:46:48Z" + content=""" +Removing the db and running `fsck` seems to have fixed the problem. I really appreciate it. I do think that I unlocked and then re-locked some of the affected files, but I think only after I noticed that they were behaving strangely---in particular, I think I only did this with the affected files that were not `fsck`ing correctly (and this was before I realized they were not `fsck`ing correctly), not with e.g. the Car Seat Headrest song. + +I didn't get the chance to fill in the \"Have you had any luck using git-annex before\" part of the standard bug report, so I thought I should add that here: Yes, I've used git-annex regularly for quite a while now. It's an inspiring piece of open-source software. I'm always finding new things it can do. Thank you for creating it, and thanks for your help with this issue! +"""]] -- cgit v1.2.3